On Sunday, May 26, 2013 5:52:49 PM UTC-5, skeept wrote: > > > I now understand why I claimed that my version supports -f. > > If I go to the folder where gvim.exe is and run .\gvim -f it does NOT support > this option. > > > > So I realized that when I type gvim in cmd I am actually running gvim.bat > which is installed in \windows. > > So if you explicitly run "gvim.bat -f" it should work, but if you run > "gvim.exe -f " it shouldn't work. >
NICE! Thanks for investigating, this was really confusing, and the new note in the help makes it even more so. Testing shows that you're right, of course, and running the Cream build directly from Program Files (x86)\vim\vim73 instead of through the .bat file does NOT support the -f argument. The key is the "/wait" given to the start command (and I assume the "/w" for non-NT systems) in gvim.bat (and other *vim*.bat files added by the installer). The help should probably mention the dependence on a cmd.exe feature in the .bat file rather than native support on Windows, instead of a cryptic "not always supported" note. -- -- 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.
