wrote:
>
> On Unix, you can compile Vim yourself, see
> http://vim.wikia.com/wiki/Getting_the_Vim_source_with_Mercurial
> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm
>
Both of these assume the "make install" command will work, i.e. you
have admin/sudo/root access to the system. Building without such
access is (I gather) much harder. From the investigation I did a few
months ago, it appears you will need to download and compile all the
dependent libraries if any are missing in addition to compiling Vim.
And all of this will need to be done using a non-default build prefix.
I haven't gotten around to trying, yet.
> If you don't have admin rights on the Unix system, you should convince
> an admin that it is more than time to upgrade his software. You might
> also (as a temporary stopgap measure, if you have access to a compiler)
> compile a modern Vim and install it in your $HOME directory.
>
This sounds like a good idea, and one would think IT departments would
be "all over that" as they say, but in my case at least, even after I
pointed to a few specific EXPLOITABLE security flaws in old Vims
(related to modeline parsing if I recall), my IT department refused to
install any Vim more recent than some flavor of 6.2 which comes on the
"companion CD" for the Solaris install. I was told if I wanted
anything more recent I would need to compile it myself, though I would
be welcome to share it with others if I got something working.
So mostly I've gotten very careful about checking for features in
my .vimrc and plugins before using them, since on my Windows PC I have
the latest Cream build installed pretty much at all times. I do mean
to get around to compiling my own at some point, but I have not yet
set aside the day or two it will probably take to figure out.
--
You received this message from the "vim_use" 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
No comments:
Post a Comment