Setting winhighlight conflicts with other plugins about deadcolumn.nvim HOT 5 CLOSED

I'll see if i can do something about it.

Thank you for the nice plugin!

from deadcolumn.nvim.

Thanks for reporting this issue. I doubt if there's anything we can do for this issue given how winhl and highlight namespace work in nvim. Switching to nvim_win_set_hl_ns requires heavy refactor and I have no intention to do this because. I don't use ccc.nvim

from deadcolumn.nvim.

I checked the API. This isn't possible to have several namespaces set simultaneously for a window by nvim_win_set_hl_ns. So switching to nvim_win_set_hl_ns won't fix the problem.

I see only two way of fixing this:

• Set highlight globally and manage colorcolumn manually (to show / hide it)
• Use virtual text

Edit:
The last nvim_win_set_hl_ns always overrides previous nvim_win_set_hl_ns

from deadcolumn.nvim.

Set highlight globally and manage colorcolumn manually (to show / hide it)

Before commit ce15b17 deadcolimn manage colorcolumn manually, but this method is proven unreliable and can easily cause confusion and bugs. Nvim/Vim uses a very complex mechanism to set options, especially for global-local options like colorcolumn (see :h global-local) and that's why I refactored this plugin to use winhl instead of managing colorcolumn manually.

Use virtual text

Needs complete rewrite.

from deadcolumn.nvim.

The only way I see to fix this is requiring ccc.nvim to switch to winhl. One can append/remove hlgroup mapping to winhl without affecting existing hl mappings, see :h vim.opt:append(), :h vim.opt:remove().

from deadcolumn.nvim.