Thank you, Tony. but my Vim works well when it is working with _vimrc or blahblah.vim. I just wanted Vim to keep the syntax-highlighting made by ':setlocal filetype=vim'. but Vim loses syntax-highlighting when ':bnext'|':bprevious' command is given. I thought it's a bug. isn't it a bug? be happy.
p.s. execuse me for my poor english speaking skill. :q 2009/2/6 Tony Mechelynck <[email protected]> > > On 06/02/09 07:53, 듀르 wrote: > > I loaded a file in which some vim-scripts are and I did ':setlocal > > filetype=vim' then I saw beautiful syntax-highlighting. :) > > but win32-gvim didn't keep it up. I did ':bnext' and ':bprevious' > > several times and i found that win32-gvim didn't keep syntax- > > highlighting up. win32-gvim just regards the filename not filetype > > (option value) when it's doing :bnext and :bprevious. > > Check whether your vimrc includes either > > runtime vimrc_example.vim > > (or "source $VIMRUNTIME/vimrc_example.vim", without the quotes, which > amounts to the same thing), or at least > > syntax on > > ; to the latter I recommend to add > > filetype plugin on > > or, depending on your indenting preferences, > > filetype plugin indent on > > Also, check that each of your scripts has either the .vim extension or > one of the names vimrc .vimrc _vimrc gvimrc .gvimrc _gvimrc .exrc _exrc > > With the above, any file which Vim knows how to highlight will be > highlighted. > > > Best regards, > Tony. > -- > How long a minute is depends on which side of the bathroom door you're > on. > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
