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
Some linters do not provide an end_col, so they don't get underlined even if vim.diagnostics is configured to do so.
In VSCode, the editor essentially sets a fake end column to the end of the line on which the error occurs, so that there's still an underline visible. It would be useful if nvim-lint offered a similar option via configuration. This makes it much easier to identify where the issue begins.
The text was updated successfully, but these errors were encountered:
I think this might be something to add in nvim core - an option that causes nvim to underline to the eol if end_col is absent in the vim.Diagnostic structure.
Then it could likely get configured via vim.diagnostic.config { underline = {...} }
Could you open a feature request in the neovim repo?
Some linters do not provide an
end_col
, so they don't get underlined even ifvim.diagnostics
is configured to do so.In VSCode, the editor essentially sets a fake end column to the end of the line on which the error occurs, so that there's still an underline visible. It would be useful if nvim-lint offered a similar option via configuration. This makes it much easier to identify where the issue begins.
The text was updated successfully, but these errors were encountered: