On Monday, July 29, 2013 9:51:43 PM UTC+8, Ben Fritz wrote: > On Monday, July 29, 2013 4:16:49 AM UTC-5, 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 > > Does your .vimrc show up in the output of :scriptnames? > > What does ":verbose set compatible?" say?
Don't know whether it is the same case. Just for your information. My path is: ....\vim\vim32 vim contains vimrc file only vim32 contains all other files like gvim.exe, vim.exe and all other directories like color, doc, and plugins, etc. When I put vimrc in vim directory like above, vim seems not finding the vimrc and use all default options, and ":verbose set compatible?" says "compatible" When I move vimrc to vim32, same directory as gvim.exe and vim.exe, everything works normally as before like 7.3, And ":verbose set compatible?" says "nocompatible Last set from ....\vim\vim73\_vimrc" Both gvim and vim I tested have the same problem above. I am testing vim 7.4b on Windows 7 64-bit English version. -- -- 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.
