There are actually some issues with colour output in other CLI applications, I suggest you to go and read Seebi article about dircolors and an ongoing(?) discussion on the solarized github issue tracker. Anyway, to use the 'fallback' you have to change the lines to the following: set t_Co=256
Yeah, weird, most people would think that 256 > 16. Contrary to what everyone could think, the 256 colour scheme is actually the 'fallback' being the 16 one the default. In my experience the 256 colour version is better (I like more grey background over a blue one but that's personal taste :P). The line set g:solarized_termcolors=16 is the default, so you can put it or not: it won't make any difference. But I rather be explicit than implicit (specially if you are going to sync your files between multiple computers). Over 250 terminal color schemes/themes for iTerm/iTerm2. Normally, the set t_Co=16 line is not necessary because most terminal emulators only support 16 colours (terminator for example). The correct configuration is the following (at least for the dark scheme): ] The problem is that that palette isn't right either :P, the correct one is the one a guy posted in an issue on that same repo. In terminator there is a github repo that holds the colour configuration for the dark and light scheme. If you opt to use some Vim plugin manager instead, the following should be added to your vimrc, rather than the above, for the color scheme to be loaded correctly: set backgrounddark autocmd. As Ethan Schoonover pointed out in his vim colorscheme readme, to make the colorscheme work first you have to configure your terminal colour palette. To use a Solarized 8 color scheme, set the background ( dark or light) then load the variant you want, e.g.: set backgrounddark colorscheme solarized8.
0 kommentar(er)
