On 27/12/13 00:39, 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.
What I do under Linux is create a link "latest" in $VIM pointing to the
current $VIMRUNTIME. Then (in Linux terms) /usr/local/share/vim/latest
means (at the moment) /usr/local/share/vim/vim74. It also means, of
course, that there is one more thing I must remember to do manually
after installing a new version of Vim; but any additional links pointing
to /usr/local/share/vim/latest/anything should go on working with no
further ado.
Something similar ought to work in recent versions of Windows but I
don't know the details. I'm not even sure it's properly documented.
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
57. You begin to wonder how on earth your service provider is allowed to
call
200 hours per month "unlimited."
--
--
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.
