From: Steve Hall <digitect@da...> - 2009-02-13 16:28:13
From: Benct Philip Jonsson, Thu, February 12, 2009 8:17 am
> A while ago I downloaded a custom syntax file
> -- let's call it foo.vim -- and put it in
> ~/.vim/syntax/. and a file consisting of
> autocmd Bufread,BufNewFile *.foo set filetype=foo
> in ~/.vim/ftdetect Everything worked just fine until
> yesterday when I decided to do some changes to the
> syntax file, adding some match statements and their
> corresponding hi statements. Previously the high-
> lighting patterns defined in ~/.vim/syntax/foo.vim
> worked out of the box when I opened a .foo file, but
> now I have to explicitly :set filetype=foo to get the
> new highlighting patterns, getting only the old ones
> out of the box. I guess another version of the syntax
> file is lying around somewhere and confusing vim
> -- only I cannot find it(*). What do you think is
> the problem?
You might have meant the Vim list for this, but if you enter
:scriptnames at the commandline it will show you everything sourced in
order to find the errant script.
Steve Hall [ digitect dancingpaper com ]
:: Cream... usability for Vim
Get latest updates about Open Source Projects, Conferences and News.