-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Can't define color palette solely in Xresources with g:gruvbox_termcolors = 16 #130
Comments
@danijar That's really nice feature to have which I've been thinking about recently too. |
Thanks. For the background color, gruvbox seems to use |
Well, actually it shouldn't |
@morhetz how's this going? I'd really like this to happen, any way I can help? |
For anyone still curious about this, Vim automatically sets |
Sorry for the double post, I've been looking into the other issue. Unfortunately it looks like the color0/background confusion is more difficult to solve. Vim can only get the colors 0-15 through 16 color terminal codes. The 'fg' and 'bg' colors are based on the Notice that the terminal has colors 0-15 which makes 16 colors, the full 16 color palette, not including foreground and background. Foreground and background in a real 16 color terminal would just be set to 0 (black) or 15 (white). So there is not a color code specifically for the color you set to your foreground or background color. You would normally be expected to set See You will have to set color0 to the background color if you want gruvbox to have the correct background. |
I would like to have Xresources as the single place to define my system-wide color palette and have Vim use that by setting
let g:gruvbox_termcolors = 16
. However:set background=dark
orset background=light
in my Vim configuration, depending on the Xresources color scheme. Otherwise, the cursor line has the opposite color.let g:gruvbox_termcolors = 16
.So I can't just change the Xresources colors to change my color scheme, but also have to edit the Vim configuration. Is there a way around these two issues?
The text was updated successfully, but these errors were encountered: