tag 430372 confirmed upstream thanks On 6/23/07, Pieter-Tjerk de Boer <[EMAIL PROTECTED]> wrote:
When starting vim on a file whose name ends in .v (a file containing Verilog code), the following error message appears:
This is happening because the verilog ftplugin script expects Vim to understand line-continuations. This is usually the case except when Vim is run in vi-compatible mode or the C flag has specifically been added to the 'cpoptions' option. I'll make a patch for the ftplugin so that it locally removes the C flag while running, apply it to the package in unstable and forward it upstream. This isn't a big enough problem to warrant an update for the Etch package. On a Debian system, you shouldn't run into this problem unless you're explicitly running Vim in vi-compatible mode (by ":set compatible"/":set cp") or are using the vim.tiny binary (either because vim-tiny is the only Vim variant installed or because you configured the alternatives to use it) and invoking it as vi. Either way, adding ":set cpoptions-=C" in your ~/.vimrc will work around the syntax script. James -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
