Closed CaffeineViking closed 4 months ago
Feel free to close the issue if the change was intentional.
This change originates from https://github.com/sainnhe/sonokai/issues/104, for context. It was indeed intentional, however SpecialKey
is not supposed to affect listchars
.^1
I was able to reproduce, and to find the root cause.
listchars
is highlighted by Whitespace
, whereas SpecialKey
is reserved for other special characters (mostly escapes like ^M
in files with the DOS file format).Whitespace
doesn't exist. SpecialKey
is used both for the special characters mentioned above and for listchars
.This is what trailing whitespaces look like in Neovim both with Neovim's defaults and with the listchars
from your vimrc:
I'm pushing a fix to master
. Thanks for reporting! 🙌
Wow, it's already been fixed. Thank you @antoineco!
I have done the following steps before reporting this issue:
Operating system/version
Windows 10
GUI client/version
gVim 9.1
Feature matrix
Minimal vimrc that can reproduce this bug.
Steps to reproduce this bug using minimal vimrc
Expected behavior
Trailing whitespace is shown in a "dim" gray. Orange for trailing whitespace is a bit too distracting.
Screenshot below is from
colorscheme gruvbox
since I can't figure out what is causing gruvbox-material to look strange, but this is also how gruvbox-material showed trailing whitespaces not so long ago. I don't know which change caused the issue (and if it was intentional or not). This must be a very recent change, as I did not experience this ~1 or 2 months ago.Actual behavior
Trailing whitespace shows as orange.