The problem is that too many colorschemes these days are not cterm-conscious: they assume that you have a lot of colours at your disposal and sometimes even that you are using gvim — and yet, Vim, as an editor, is still extremely useful for some tasks that have to be done with no GUI interface; one of these tasks would be rescuing a failed software upgrade, where you can't rely on a functioning X11 server: then you are left with the "bare bones" console which usually has only 8 background and 16 foreground colors, and uses the cterm= ctermbg= ctermfg= settings of the :hi command, not the gui= guibg= guifg= guisp= settings. Another such task would be tweaking settings on a server where no X11 package is installed (and usually no screen or keyboard either but the sysadmin added them for the occasion).
IMHO Vim's default colors are quite good, though not perfect (nothing is perfect) for both cterm and gui (I haven't had the occasion to test the term= colors for lack of the necessary monochrome-terminal hardware in the days since I've known Vim) so I use an owncoded colorscheme which defines only what I regard as insufficient in the default colors (and no shame on Bram: de coloribus non est disputandum). When running Console Vim in a terminal which is capable of 256 colors (such as konsole or xterm) I supplement this colorscheme (which you'll find attached; feel free to use it or not, and if you do, to adapt it to your own use case; if you want to try it, its home is in ~/.vim/colors on a Unix-like system, or in ~/vimfiles/colors on a Windows system) with the CSApprox plugin (available at vim.org), so in that case I get the same colors, or as close as possible and almost indistinguishable to my eye, in Vim in konsole or xterm and in gvim. (I wrote that colorscheme before the 'termguicolors' option was available and this way I don't depend on the +termguicolors feature being compiled-in.) Of course, in the 8/16 bare-bones console (where CSApprox detects that &t_Co < 88 and disables itself) the colors are very different but at least they are distinct. Best regards, Tony. -- -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_use" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
almost-default.vim
Description: Binary data
