Re: autocmd bug?

2007-03-27 Thread A.J.Mechelynck
Jürgen Krämer wrote: [...] the FileType event is only fired once with the exact filetype you specified in your set command, so you must additionally define the following autocommand: autocmd FileType c.doxygen setlocal cindent number cursorline Regards, Jürgen If that is true, doesn't it

Re: autocmd bug?

2007-03-27 Thread Jürgen Krämer
Hi, A.J.Mechelynck wrote: Jürgen Krämer wrote: [...] the FileType event is only fired once with the exact filetype you specified in your set command, so you must additionally define the following autocommand: autocmd FileType c.doxygen setlocal cindent number cursorline If that is

Re: autocmd bug?

2007-03-27 Thread A.J.Mechelynck
Jürgen Krämer wrote: [...] Nice idea (esp. the recursion), but alas it's not that simple, because the pattern only accepts wildcards (not regular expressions) and if it did, the subpatterns would probably not be recognized in the command. But your command gave me an idea -- the following should

Re: autocmd bug?

2007-03-26 Thread Yakov Lerner
On 3/26/07, Michael Wookey [EMAIL PROTECTED] wrote: I have the following in my .vimrc: filetype plugin indent on autocmd FileType c,h,cpp,hpp,cs setlocal cindent number cursorline If I have a new buffer and set the filetype as follows, everything works just fine: :set filetype=c

RE: autocmd bug?

2007-03-26 Thread Michael Wookey
I have the following in my .vimrc: filetype plugin indent on autocmd FileType c,h,cpp,hpp,cs setlocal cindent number cursorline If I have a new buffer and set the filetype as follows, everything works just fine: :set filetype=c However, if I have a new buffer

Re: autocmd bug?

2007-03-26 Thread Jürgen Krämer
Hi, Michael Wookey schrieb: I have the following in my .vimrc: filetype plugin indent on autocmd FileType c,h,cpp,hpp,cs setlocal cindent number cursorline If I have a new buffer and set the filetype as follows, everything works just fine: :set filetype=c However, if