Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Revamp diagnostics highlights #995

Merged
merged 20 commits into from
Jan 1, 2021
Merged

Conversation

prabirshrestha
Copy link
Owner

@prabirshrestha prabirshrestha commented Dec 31, 2020

This is part of Diagnostics Revamp and is about highlighting diagnostics information. It implements few feature asks as well as bugs.

  • unify vim's textprops and neovim's nvim_buf_add_higlight
  • update to using callbag
  • support neovim via nvim_buf_add_higlight
  • support vim via textprops
  • allow to disable in insert mode via let g:lsp_diagnostics_highlights_insert_mode_enabled = 0
  • add support for debounce via let lsp_diagnostics_highlights_delay = 5000
  • fix bug in neovim where if startline == endline && startcol == endcol nothing gets highlighted
  • fix bug in neovim where we highlight the entire range instead of always assuming endcol is end of column for start line.
  • respect lsp#internal#diagnostics#state#_is_enabled_for_buffer
  • make highlighting consistent across vim/neovim/vscode
  • update docs

It is a breaking change due to flag name changes but is necessary to unify and make it consistent.

@prabirshrestha prabirshrestha force-pushed the diagnostics-highlights branch from e21c061 to f4435cf Compare January 1, 2021 06:16
@prabirshrestha prabirshrestha changed the title [WIP: Do not merge] revamp diagnostics highlights Revamp diagnostics highlights Jan 1, 2021
@prabirshrestha prabirshrestha merged commit efd07d8 into master Jan 1, 2021
@prabirshrestha prabirshrestha deleted the diagnostics-highlights branch January 1, 2021 07:13
seandewar added a commit to seandewar/dotfiles that referenced this pull request Feb 25, 2021
…l(), remove UTF symbols

LSP highlights work a lot better since the revamp
(prabirshrestha/vim-lsp#995), so we're happy to re-enable them (to be
exact, the option name changed anyway, so the disable had no effect
since the update)

UTF just doesn't play nicely with some terminal/GUI configurations for
Vim/Neovim, so just use plain-old ASCII until support is more reliable
# for free to join this conversation on GitHub. Already have an account? # to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant