On 08/04/10 12:53, ron wrote:
On Apr 8, 11:41 am, Tony Mechelynck<[email protected]>
wrote:
:help has()
:help feature-list
Thanks, I know that ...
It turns out it was Programmer Error (on my part). My NSIS installer
was not running with high enough privileges to set VIMRUNTIME in the
environment. By the way, requiring that to be set is really odd ...
but anyway, my stuff now works on Vista and Windows7
Thanks again,
Ron
You should not need to set VIMRUNTIME in the permanent environment; on
Windows, Vim sets it (for itself and the processes it spawns, but not
permanently), usually to the directory from which it was loaded
("C:\Program Files\vim\vim72" or similar). In addition, that setting
changes from one version to the next so it really should _not_ be
permanent (if you run two different Vims in parallel, each of them
should set VIMRUNTIME in its own environment according to its version).
Similarly Vim sets VIM, usually to the parent of VIMRUNTIME. You may
want to set it if you want to access, let's say, $VIM/vimfiles from the
command (shell) prompt, but it is not necessary.
...and if you mean that setting variables temporarily in one's own
environment requires superuser privileges on Windows Vista and later,
that's one more proof (if I needed any) that Gates & Co. don't
understand a thing to what security means: such a measure won't make
fewer users set environment variables, it will make more of them grab
superuser privs permanently, which is the opposite of the desired result.
Best regards,
Tony.
--
The men sat sipping their tea in silence. After a while the
klutz said, "Life is like a bowl of sour cream."
"Like a bowl of sour cream?" asked the other. "Why?"
"How should I know? What am I, a philosopher?"
--
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
To unsubscribe, reply using "remove me" as the subject.
