The command for opening the clojure-lsp log file doesn't (always?) work

Open bpringe opened this issue 2 years ago • 3 comments

It doesn't work for me on MacOS. I think it hasn't worked in a while for me. It seems it should work even if the log path is set dynamically by clojure-lsp since it uses the log path reported from the server's returned info. Either Calva is doing something incorrectly or clojure-lsp isn't returning the right path.

Jul 30 '23 23:07 bpringe

It could also be that the log file has grown beyond 50Mb and we fail to catch the error from VS Code refusing to open it.

Dec 06 '23 19:12 PEZ

Hmm... maybe to have a more reliable solution, we should just print the path somewhere for the user and let them open it however they want to.

Dec 06 '23 19:12 bpringe

Indeed. Command-clicking the path will open it in VS Code, and probably display a proper error message.

Dec 06 '23 20:12 PEZ