On Wed, 15 Feb 2012 08:48:49 +0100 Christian Brabandt <[email protected]> wrote:
> Hi john! > > :let cobol_legacy_code = 1 > > See, if this variable exists in your cobol file and enter: > > :echo cobol_legacy_code > > If you don't get an error, simply unlet that varible: > > :unlet cobol_legacy_code > > and do a > > :filetype detect > > The highlighting should than vanish. You then need to find out, > where you set this variable (I suspect either in your .vimrc, > in a ftplugin/cobol.vim or even after/ftplugin/cobol.vim file) > > regards, Christian > Well I write in COBOL 85 in the traditional fixed format. See my previous example. I started with pre-COBOL 68, in 1968. The IF statement and the AT END statements were legal then and still are legal in all the compilers I have used. I am reasonably certain they were legal in the very first COBOL compiler written by Grace Murray Hopper and her crew. So there is a fault in cobol.vim. Yes, I have cobol_legacy_code set. That should not cause IF and END to be highlighted as errors. There is a problem with cobol.vim, like it or not. If I unset cobol_legacy_code, IF no longer causes errors. But line numbers in columns 1-6 are now highlighted as errors. I upgraded to vim 7.3 but still have the same error. I will try disabling my .vimrc file and see if that helps. -- John Culleton Free list of books for self-publishers: http://wexfordpress.net/shortlist.html "Create Book Covers with Scribus" http://www.booklocker.com/books/4055.html -- You received this message from the "vim_use" 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
