Thilo Six wrote the following on 07.07.2011 14:11
-- <snip> --
A little follow up as i just noticed i had an old filetype.vim in production.
I reverified with a new filetype.vim from mercurial and the conclusion below is
still true but line numbers changed slightly.
> 'Config.in' is by default detected as filetype 'conf' which is afaict s.th.
> like
> a catch-all filetype for everything that isn't defined in 'filetype.vim'
> already.
>
> Adding 'Config.in' to filetype.vim (actually line 936 over here) still leads
> to
^- 953
> ft=conf, no matter how many lines of comments are on top of the file.
> This is due the code block starting at line 2463 in filetype.vim.
^- 2523
>
> Adding the line:
> ,----[ .vimrc ]--------
>
> au BufNewFile,BufRead Kconfig,Kconfig.debug,Config.in setl ft=kconfig
> `---------------------------------------------
>
> does what you want.
>
> But actually i am not able to reproduce the error you described with:
>> HOWEVER, for some strange reason if there is a comment at the top of
>> the file, the file is no longer recognized as a Kconfig file, but as
>> a <something> source file.
>
> Guess there must be some local settings {and,or} plugins that do that.
>
> For now i don't see a bug in default vim filetype settings.
>
> HTH
--
bye Thilo
4096R/0xC70B1A8F
721B 1BA0 095C 1ABA 3FC6 7C18 89A4 A2A0 C70B 1A8F
--
You received this message from the "vim_dev" 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
