On Monday, 29 July 2013 11:16:49 UTC+2, anst wrote: > On windows 7 64-bit I get this behaviour both in gvim and vim. > The options I have in the vimrc file are read, so this seems like a bug. > > Regards > Andreas Stabel
As I stated in my first post the vimrc file is read so it is not a problem with paths. I have a copy of the _vimrc in ...\vim and one called vimrc in ...\vim\vim32 Stephen Lee suggested I remove the copy in ...\vim, but this didn't change anything. The funny thing is that if I put nocp in the vimrc file I get nocompatible ! This solves my problem, so if it is not considered serious this need not be treated as a bug. Thanks for all suggestions Andreas -- -- 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
