Ben Schmidt wrote:
>> __________________ From cobol.vim _______________________
>>
>> syn match cobolBadLine "^.\{6\}[^ D\-*$/].*"hs=s+6
>>
>> " If comment mark somehow gets into column past Column 7.
>> syn match cobolBadLine "^.\{6\}\s\+\*.*"
>
> My cobol.vim is dated as follows
>
> " $Id: cobol.vim,v 1.2 2007/05/05 18:23:43 vimboss Exp $
>
> It contains
>
> syn match cobolBadLine "\s\+\*.*" contained
>
> which I changed into
>
> syn match cobolBadLine "\s\+\*\%<13c.*" contained
>
> and it seems to work. Something similar should work in your syntax file,
> changing
>
> syn match cobolBadLine "^.\{6\}\s\+\*.*"
>
> into
>
> syn match cobolBadLine "^.\{6\}\s\+\*\%<13c.*"
>
> perhaps. Not really knowing any COBOL (and kinda glad about it, to be
> honest), I don't know if it's the best way to fit it in, but it should
> do what you described.
>
> Given that it appears your runtime file is out of date, you may want to
> upgrade it and/or Vim itself (particularly if you want that variable
> tabstop thing--compiling Vim is really easy). There may be other
> improvements that will help you.
DISCLAIMER: Changing your Vim runtime files really isn't recommended.
Better is to make a copy of the file into ~/.vim/syntax/whatever.vim (or
the appropriate subdirectory of ~/.vim) and change that. Then your
changes won't get lost when Vim or your runtimes are updated. If you're
on Windows, $HOME\vimfiles is the place, not ~/.vim.
Even better is to figure out a short piece of code that can be applied
in addition to the existing code, and just put that snippet in
~/.vim/syntax/whatever.vim or ~/.vim/after/syntax/whatever.vim which
means you still get the benefits when the runtimes are updated, but your
modifications persist, too.
Ben.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
