<snip>

> Do you have a real world example. I would like to have a look at
> that.
> The example would include the file you want to detect and the path
> where one
> would find it. Thanks.

Sure, I'm only attaching the Config.in file.  To make the change
to the filetype.vim file is simple, just add *onfig.in to the
Kconfig au line (around 946).

The attached file was originally from the Linux kernel source --
the drivers dir Kconfig file I renamed to Config.in, then added
a comment block to the top.  You can reproduce using any Kconfig
file renamed to Config.in (which is what BuildRoot calls their
Kconfig files) and throw in a comment block of about 4 lines or so.

Hopefully, the attachment will not be mangled by LookOut, but if
so, you have the formula to reproduce it.

Andy

> 
> Generally in filetype.vim the first match takes it:
> 
> ,----[ :h setf   ]--------
> 
> :setf[iletype] {filetype}                     *:setf* *:setfiletype*
>                       Set the 'filetype' option to {filetype}, but only
> if
>                       not done yet in a sequence of (nested)
> autocommands.
>                       This is short for: >
> `---------------------------------------------
> 
> 
> --
> 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

-- 
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

Attachment: Config.in
Description: Config.in

Raspunde prin e-mail lui