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 :: http://cream.sourceforge.net ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ cream-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/cream-general
