-
Notifications
You must be signed in to change notification settings - Fork 184
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Logging panel is too short #1810
Comments
There is the Though maybe if the server has so much output, it would be best to also support logging to file. |
I could be wrong, but I think that setting is for line length, not total number of lines. At any rate, setting it to zero did not change this. |
Well, without it the log would fill up with no end. Could easily reach megabytes of text. Also I guess the syntax highlighting would stop working after some point. |
I am trying to debug an issue with
rust-analyzer
. According to the RA docs I can get some useful information out of it by increasing logging. When I do that, by the time I can open the LSP log panel, the relevant messages are gone.To Reproduce
Steps to reproduce the behavior:
Go to Preferences > Package Settings > LSP > Settings.
Add:
(Note that the
command
will probably have to change depending on how you installed RA.)Restart the language server, or open a Rust project.
Open the LSP log panel.
Watch as the relevant messages disappear out of the top of the panel.
I am not just talking about scrolling here, scrolling the panel contents up will still hit this limit.
This information is not available via the
remote
log setting.Expected behavior
I would expect to be able to set this somewhere.
Screenshots
Here's a GIF! I did not want to capture my actual code, but shortly after the GIF starts, I am restarting the RA language server.
Environment:
rust-analyzer
The text was updated successfully, but these errors were encountered: