Replies: 4 comments 3 replies
-
do you mean the |
Beta Was this translation helpful? Give feedback.
-
Ah, yes, that seems to be the right setting (0 for me, 1 seems to still add comments for errors, 2 for errors and warnings). It might be useful to update the docs to include some language about how this will usually be a comment in the used language, so people like me who search for "comment" and few other strings can find the text. I definitely would not expect comments to be be added to my code from the option's description here: Line 2291 in a18472c Either way, thanks a bunch! |
Beta Was this translation helpful? Give feedback.
-
What is an LSP in this context? FWIW, I was editing Go code using vim 8. |
Beta Was this translation helpful? Give feedback.
-
So with the default setting, a spurious whereas in older versions (and with g:ale_virtualtext_cursor=0) it looks like this: Note how the latter is much cleaner/less distracting, but yet conveys the same information. Fortunately, writing the file will not include the comments added. I guess in some contexts, adding the comment allows for more useful information or something? Anyway, I can have my old statusline behaviour back, and that's what I care about :) |
Beta Was this translation helpful? Give feedback.
-
I personally find that super disruptive, especially since I am using vim, and the gutter indicator (and status line info when I go there) are much less disruptive and easier to use when coding (as opposed to editing). The added comments are a storm of info I don't care about most of the time (when coding, there are a lot fewer moments where the code is fine than there are moments when e.g. a loop is half-written).
I tried finding an option to go to the old behavior (marker and status line only), but to no avail.
Beta Was this translation helpful? Give feedback.
All reactions