my custom is dark solarized with my default background; solarized has a nice syntax.
wombat does not work but wombat256 works could it be that only 256 color themes work?
you do have set t_Co=256 maked wouldnt it depend on you terminal and thus A 256 terminal would work with 256 themes and backwords compadible. maybe somthing like
set term=xterm-256color
just a quess
ya solarized looks pretty cool and ya it should be backward compatible I believe thisoldman hit the nail on the head.
]]>Some colorschemes are gvim only, they will not work in a terminal emulator. In xterm, run the following (that's a lowercase 'L' in the first command):
$ grep -l cterm ~/.vim/colors/*.vim ## Colorschemes that should work $ grep -L cterm ~/.vim/colors/*.vim ## Colorschemes that will not work
Please don't set the TERM variable from a dotfile. Use xterm's 'termName' resource:
$ xterm -tn xterm-256color ## Command line -- OR -- ! Resource file: xterm*termName: xterm-256color
Ah makes sense! Thanks for the dotfile advice just changed.
]]>$ grep -l cterm ~/.vim/colors/*.vim ## Colorschemes that should work
$ grep -L cterm ~/.vim/colors/*.vim ## Colorschemes that will not work
Please don't set the TERM variable from a dotfile. Use xterm's 'termName' resource:
$ xterm -tn xterm-256color ## Command line
-- OR --
! Resource file:
xterm*termName: xterm-256color
wombat does not work but wombat256 works could it be that only 256 color themes work?
you do have set t_Co=256 maked wouldnt it depend on you terminal and thus A 256 terminal would work with 256 themes and backwords compadible. maybe somthing like
set term=xterm-256color
just a quess
]]>so the txt highlilghting seems to be fine now, just removed and reinstalled vim, but backgrounds are giving me an issue.
So just randomly doing :color <someColorScheme> these are the ones that actually change the background from the ones I tested:
Mustang
autumn
autumn2
autumnleaf
baycolmb
...
wombat does not work but wombat256 works could it be that only 256 color themes work?
So ya I think it has to do with either being 256 or there is something else in the colorsheme.vim that I am not addressing.
Will definitely learn more about the files as I want to cobble together a few of my own.
If anyone has any ideas would love to hear.
cheers.
]]>Try adding '~/.vim' to your runtime path. In your .vimrc:
set nocompatible set runtimepath=~/.vim,$VIM/vimfiles,$VIMRUNTIME set t_Co=256 syntax on colorscheme zmrok
just copy and pasted into my .vimrc did not remedy the situtation.
once again the oddity is like
:color blue
:color desert
work fine which I believe are the stock vim colorschemes that vim works with but additional ones do not work.
You can tab through them and it shows there are set
:color <tab>
but the changes do not take efffect... Could it be that somehow my .Xresources is overwriting them somehow? And if this is the case why wouldn't they prevent the stock color schemes?
Anyway I do appreciate the suggestions.
]]>Just in case it was not a mere typo. Vim looks in the ~/vim/colors directory (not color) for colorschemes.
I will go even further and say: ~/.vim/colors...
]]>set nocompatible
set runtimepath=~/.vim,$VIM/vimfiles,$VIMRUNTIME
set t_Co=256
syntax on
colorscheme zmrok
what does your vimrc look like?
syntax on
set t_Co=256
colorscheme zmrok
customs work for me
mkdir -p ~/vim/color
then just put it in the color dir and add it to vimrc with no .vim extension
yup exactly what I have done thus my confusion...
]]>mkdir -p ~/vim/color
then just put it in the color dir and add it to vimrc with no .vim extension
]]>