James Vega wrote: > On Wed, Feb 06, 2008 at 09:43:33PM +0100, Bram Moolenaar wrote: > > The main reason to do it this way is that when a startup script contains > > "set nocp" the following lines often depend on this. If one would start > > "vim -C" and the -C would cause the "set nocp" line to be ignored, the > > rest of the script would be misinterpreted. Especially for ":map" > > commands with things like "<C-A>". With 'nocompatible' this means > > CTRL-A, with 'compatible' this is 5 separate characters. > > The initial bug was specifically that "vim -C" with "set nocp" in a > startup script resulted in a Vim session that didn't have 'compatible' > set as per the man page. I notice that the help for -C indicates the > ":set nocompatible" command will override -C so maybe it would be > sufficient to add this to the man page as well. A similar note should > be added to the help/man page for -N. > > This would be a simpler solution, although I still think that if the > user is specifically requesting (no)compatible mode at the command line, > they should be able to deal with side-effects it may have on startup > scripts.
Well, a possible solution would be to do "set compatible" after all the startup stuff is done. I suppose that would work as expected. -- hundred-and-one symptoms of being an internet addict: 3. Your bookmark takes 15 minutes to scroll from top to bottom. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
