ctermfg so that your group would automatically work on both GUIs and terminals). If you want to create your own highlight group that uses these values, then you will probably have to edit it into your copy of colors/solarized.vim (though you may want to use s:fg_base00/ s:bg_base00 instead of s:base00 since the former cover guifg vs. When you're not running the terminal Solarized scheme, you tell it to try to use a degraded palette. If diagrams are not refreshing quickly or not at all, the PlantUML server may be.

So I remove from /.vimrc call togglebgmap('') and replaced it with what most google/superuser/vim. vim solarized

Solarized has an exact palette it expects that is actually just based on 16 colors. You can switch to VIM or Emacs mode if you are an old school unix geek. but this doesnt work because it changes the colorscheme from solarized to default (my intention was to toggle only in solarized between dark and light). The defining script “exports” the color values as a part of the highlight groups that it defines, but does not seem to export the individual cterm/gui values it uses for each Solarized color. set backgrounddark let g:solarizedtermcolors256 colorscheme solarized. vimrc (or anywhere except the script in which they are defined: colors/solarized.vim). Variables that start with s: are script-local variables (see :help s:var), so they are not accessible in your. s:base00 to build an command string and execute it (this is basically what colors/solarized.vim does) however there is an additional problem.

When I run vim without tmux, it looks great, see below: If I add the following commands to my. You could use execute 'highlight GroupName ctermfg='. I am trying to use the solarized color scheme in VIM using gnome terminal (Ubuntu). You get E421 because s:base00 is not a number, nor a valid color name. It accepts only a literal color number, or a color name (see :help cterm-colors). The :highlight command does not evaluate ctermfg values as expressions.

Vim solarized