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
{{ message }}
This repository has been archived by the owner on Jul 6, 2021. It is now read-only.
It would be great if there was a command provided to toggle the execution of the plugin at runtime. Something like :ToggleDiagnostics.
Sometimes, especially during reshuffling code the amount of diagnostics can be quite overwhelming and easy toggle for either the total plugin or at least the virtualtext (g:diagnostic_enable_virtual_text does not have an effect when changed at runtime [as expected]).
I just wanted to throw this out there in case someone else also finds this useful 🙂
The text was updated successfully, but these errors were encountered:
I actually did something similar for a friend, which was something like :ShowCurrentLineDiagnostics to open the diagnostics for the current line (if you're on the line with error, :NextDiagnostic would go to a next line with errors and there was no way to show the current line's one)
Thanks for your input! But I believe my explanation may not have been clear enough..
I actually do use the popup with more detailed diagnostics (especially if there are multiple on one line).
But instead, my toggle would turn off all diagnostic-evaluations for the current buffer. I.e. no popups, no virtual text and no symbols. If it wouldn't be too much to implement it would be even more awesome if these three could be toggled separately too. I.e. disable popups and virtual text for current buffer but leave the symbols, etc.
It would be great if there was a command provided to toggle the execution of the plugin at runtime. Something like
:ToggleDiagnostics
.Sometimes, especially during reshuffling code the amount of diagnostics can be quite overwhelming and easy toggle for either the total plugin or at least the virtualtext (
g:diagnostic_enable_virtual_text
does not have an effect when changed at runtime [as expected]).I just wanted to throw this out there in case someone else also finds this useful 🙂
The text was updated successfully, but these errors were encountered: