Aha!
I had the following line:
let colors_name = 'danningcolors'
instead of 'dan-xterm'.
I didn't realize that the colors_name was significant, but changing it
did the trick. Making the colors_name the same as the file name made
it work as expected.
Strange that doing it 'by hand' didn't have the same effect, but now
that I know how it works, I think I'm all set.
Thanks,
-Dan
On Jul 10, 4:40 pm, Tony Mechelynck <antoine.mechely...@gmail.com>
wrote:
> On 10/07/10 21:43, Danning Ai wrote:
>
>
>
>
>
>
>
> > I have a colorscheme that I've set up, named dan-xterm, and located in
> > ~/.vim/colors/dan-xterm.vim.
>
> > It's not much different from some of the standard color schemes (I
> > started with evening) but clearly I made some mistake. I can't figure
> > out what it is, however, but here's the symptom.
>
> > If I load the colorscheme "by hand" (i.e., type ':colors dan-xterm' in
> > command mode), then it loads and looks exactly as I expect. But when
> > I put it in my .vimrc, then it doesn't work at all!
>
> > In my .vimrc, I put
>
> > :colors dan-xterm
>
> > at the end, and it doesn't give me my colors--it gives me some weird
> > combination of colors.
>
> > If I replace dan-xterm with a standard colorscheme that I've copied
> > into my ~/.vim/colors, then everything works as expected.
>
> > There's probably some issue in my colorscheme that keeps it from being
> > loaded during startup (even though it works fine later), but I am
> > baffled trying to find it. Any suggestions?
>
> > Thanks,
> > -Dan
>
> Your colorscheme should include the line
>
> let colors_name = 'dan-xterm'
> or maybe
> let colors_name = fnamemodify(expand('<sfile>'), ':t')
>
> Does it (and if the latter, outside of any function)?
>
> Best regards,
> Tony.
> --
> If God had intended Men to Smoke, He would have put Chimneys in their
> Heads.
--
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
