Hi,
You problem can be worked around with :set isk+=_
But your problem may be you are not changing the one Vim is sourceing, or
if the settings are overrideed by future scripts.
you have a filetype.vim in system wide $VIM directory or your ~/.vim
directory or vimfiles/after directory? see :h 'runtimepath'
or if there is directories like ~/.vim/ftdetect and scripts in there
overrides the default setting? see :h new-filetype
Hope that helps.
--
Sincerely, Pan, Shi Zhu. ext: 2606
"Kunapuli, Udaykumar" <[EMAIL PROTECTED]> 写于 2006-10-16 18:30:55:
> Looks like it is hard-coded. No matter what I try, VIM does
> recognize *.lib as a cobol file.
> I have deleted the occurrence of cobol and .lib in the filetype.vim
> file. But of no use.
> In fact there is no occurrence of "cobol" in any of my runtime files.
>
> The irritating thing is the search pattern, regular expression change.
> You can try hitting "*" on a word with underscore character ("_") on
> a file with .lib extension,
> you will see that it considers underscore ("_") as a distinct (non-
> word) character.
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Sunday, October 15, 2006 11:50 PM
> To: Kunapuli, Udaykumar
> Cc: vim@vim.org
> Subject: Re: VIM help for normal text files with extension .lib (on UNIX)
>
> "Kunapuli, Udaykumar" <[EMAIL PROTECTED]> 写于 2006-10-16 14:37:33:
> > Hi,
> >
> > I tried editing the filetype.vim in the runtime directory and
> > commenting the portion with the .lib extension. But it didn't work.
> >
>
>
> Are you sure you had done it right? I removed the "*.lib" and it works.
>
> this is the filetype.vim around 440 (after the "*.lib" removed)
>
> " Cobol
> au BufNewFile,BufRead *.cbl,*.cob setf cobol
>
>
> IMO, the "*.lib" is a common extension which should not be treated
> as cobol file. So just remove the relationship here.
