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

[bpringe]

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.

[PEZ]

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.

[bpringe]

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.

[PEZ]

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