On Fri, Dec 27, 2013 at 12:56 AM, Ben Fritz <[email protected]> wrote: > On Thursday, December 26, 2013 5:39:11 PM UTC-6, Adrian wrote: >> The versioned install path ($INSTALLDIR/vim74/[g]vim.exe) is a major >> annoyance on Windows. People are likely to assign file types to be opened >> with vim. However, all those assignments break once a new Vim version is >> installed (because the path changes, e.g. from vim73 to vim74). While this >> is not too hard to fix (searching for the old path using regedit), any other >> program that is configured to call Vim for something has the same problem! >> >> The easiest solution would be installing a "proxy"-like file in $INSTALLDIR >> which simply calls the exe with the same name in $INSTALLDIR/vimXY/ and >> forwards all arguments. > > You mean like the gvim.bat, vim.bat, etc. files created in C:\Windows by the > installer?
Won't that cause a console window to appear? That seems like bad behavior if my intention is to use gVim and launch it from Explorer. -John -- -- 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.
