-
Notifications
You must be signed in to change notification settings - Fork 166
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ErrorText highlight looks broken on neovim 0.10 #205
Comments
Could you please share details about your terminal emulator and colorscheme configuration? Here how the sample code renders for me on WezTerm (latest nightly) with the following colorscheme config (lazy.nvim + Neovim 0.10): {
"sainnhe/gruvbox-material",
lazy = false,
priority = 1000,
config = function()
vim.g.gruvbox_material_enable_italic = true
vim.cmd.colorscheme('gruvbox-material')
end
}, edit: the same as above with |
configuration: {
"sainnhe/gruvbox-material",
lazy = false,
priority = 1000, -- make sure to load this before all the other start plugins
config = function()
vim.g.gruvbox_material_background = "hard"
vim.g.gruvbox_material_ui_contrast = "high"
vim.g.gruvbox_material_inlay_hints_background = "dimmed"
vim.g.gruvbox_material_dim_inactive_windows = 1
vim.g.gruvbox_material_diagnostic_virtual_text = "highlighted"
-- NOTE: Needs to be called last for the settings to take effect
vim.cmd.colorscheme("gruvbox-material")
end,
}, terminal is
I checked right now and this doesn't happen on my other |
What is the output of Does it also occur if you install and enable the
|
Unfortunately yes, I use Wezterm on Windows to run my WSL2 linux, after adding |
I use WezTerm on Windows 11 and run Neovim inside WSL2 (Debian 12) too. I have to admit that I just ran out of ideas. |
I'll try poking around the wezterm community, but thank you for taking the time to help me! |
Ah that's some progress! Support for undercurl on Windows is currently only available in WezTerm nightly, so that would explain the absence of undercurl for you. |
Cross referencing |
Unless you think this report has some other value, I don't think |
I agree that there is probably not much we can do inside the colorscheme, besides changing the default style of diagnostic texts to not use undercurl. However, I am interested in the resolution. Terminal multiplexers have been historically problematic with things like italics, standout and fancy underlines. If we can have a note about Zellij inside the vimdoc, I'm all for it! |
Hm, I tried to collect info from both wezterm and zellij, and I'm not entirely sure what to make of it:
|
WezTerm has been supporting undercurl for a long time on Linux and macOS, but had a dependency on ConPTY and OpenConsole (from Windows Terminal) on Windows, which added support for undercurl only recently. Wez included those updated files on Feb. 11, whereas the latest stable was released on Feb. 3. I can't talk authoritatively about Zellij because I have never used it. I remember having a lot of similar issues with Tmux when I wasn't setting the terminfo to |
Looks like Zellij needs to work on its compatibility with Neovim 0.10 🙂 |
After switching to neovim 0.10, my lsp error highlights started looking weird (the
3600a
text):This seems consistent with what gruvbox-material uses with
diagnostic_text_highlight = 1
, but I have that option disabled in the screenshot above.The text was updated successfully, but these errors were encountered: