Danek Duvall wrote: > There are a handful of syntax files that use backslash continuation > characters without ensuring that cpoptions is missing C, so when running > vim in vi compatibility mode (such as when there's no .vimrc), you'll get > errors like > > Error detected while processing /usr/share/vim/vim73/syntax/po.vim: > line 37: > E10: \ should be followed by /, ? or & > line 39: > E10: \ should be followed by /, ? or & > > when editing a .po file and running "syn on". Most syntax scripts (at > least those that use continuation characters) execute "set cpo&vim" and > reset cpo at the end of the script, but these don't: > > autoit.vim > cmake.vim > cucumber.vim > datascript.vim > fvwm.vim > lsl.vim > mrxvtrc.vim > objc.vim > perl6.vim > php.vim > po.vim > sgmldecl.vim > taskdata.vim > taskedit.vim > tex.vim > valgrind.vim > > I'm happy to submit a patch that fixes these, but there are many scripts > outside the syntax directory that would have the same problem, and I don't > know whether these should be fixed in the vim distro or further upstream > first, so I'm looking for guidance.
Every file should mention a maintainer in the header. Please try contacting him/her first. It would be good to get this fixed. If I change my local copy it's likely overwritten whenever the maintainer sends another update. - Bram -- hundred-and-one symptoms of being an internet addict: 58. You turn on your computer and turn off your wife. /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- 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
