You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
LanguageServer.jl (and some of its dependent packages) send (all?!) info output (such as the timing summary or the packages loaded from cache) to stderr, which leads to quickly ballooning log files in clients such as Neovim since these messages are treated as actual errors.
As these are not error messages, they should be emitted accordingly (stdout, or ideally as actual LSP notifications).
The text was updated successfully, but these errors were encountered:
We can't send anything to stdout as that is used for the actual JSONRPC commutation.
Also, stderr seems exactly the right place to send (non error) log output to? In VS Code for example that ends up in the log output view for the LS which is super helpful. I guess you could run the Ls with a different log level if you don't want to see these messages?
I guess you could run the Ls with a different log level if you don't want to see these messages?
That is exactly what I'm doing; I don't expect to see these messages with a log level set to "ERROR". (No other server sends "INFO" messages by default.)
(Obviously, you could say the server is still WIP, so any use would be testing and debugging, but...)
LanguageServer.jl (and some of its dependent packages) send (all?!) info output (such as the timing summary or the packages loaded from cache) to
stderr
, which leads to quickly ballooning log files in clients such as Neovim since these messages are treated as actual errors.As these are not error messages, they should be emitted accordingly (
stdout
, or ideally as actual LSP notifications).The text was updated successfully, but these errors were encountered: