-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
VSCode: apply highlightOn
setting without a restart
#84
Comments
bors bot
added a commit
that referenced
this issue
Dec 20, 2018
302: Support tracing lsp requests. r=matklad a=DJMcNab TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway. (Continuation of #84 [#99 only disabled using it, not making sure we don't send it]). These logs can be used in https://microsoft.github.io/language-server-protocol/inspector/ Co-authored-by: DJMcNab <36049421+djmcnab@users.noreply.github.com>
bors bot
added a commit
that referenced
this issue
Dec 24, 2018
302: WIP: Support tracing lsp requests. r=DJMcNab a=DJMcNab EDIT: We need to work out a better way to handle settings before this can be merged. Help wanted TODO: Debug why decorations are sent even when highlightingOn is disabled This makes the log volume so high its impossible to work with anyway. (Continuation of #84 [#99 only disabled using it, not making sure we don't send it]). These logs can be used in https://microsoft.github.io/language-server-protocol/inspector/ Co-authored-by: DJMcNab <36049421+djmcnab@users.noreply.github.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
https://github.com/matklad/rust-analyzer/pull/83 introduced a vscode setting that makes it possible to disable rust analyzer's syntax highlighting. This setting is applied when the extension is initialized, which means that changes only take effect upon restarting vscode. It would be nice to apply changes to this settings in real time, instead of requiring a restart.
I plan to write a PR for this in the future days, but if anyone else wants to fix this just go for it and open a PR!
The text was updated successfully, but these errors were encountered: