First I want to say that I am very happy with vim. What follows are
my personal considerations about a resently published feature
request first. Secondly, a possible answer of the preceding email in
this tread (hopefully).
> USER_VIMRC, SYSTEM_VIMRC, USER_PLUGIN_DIR, SYSTEM_PLUGIN_DIR
IMHO a good idea to let one explicitly define this location rather
than find out where vim implicitly searches its configuration data.
I would use the names USER_VIM_PLUGIN_DIR and SYSTEM_VIM_PLUGIN_DIR
instead of the too general names USER_PLUGIN_DIR and SYSTEM_PLUGIN_DIR.
The idea must be: Don't let vim silently make difficult decisions:
When a path (directory or file) pointed by some of the environment
variable does not exist, then, in my opinion, vim should emit a
warning and then use some defaults rather than silently searching
its data at some other place.
When a environment variable is not defined, vim should behave in
some standard manner without emitting warnings or silently search
some configuration data.
There must be, in my opinion, a command line option that lets one
override any environment variable vim depends from.
>>What if you are run vim from removable media?
> Do you mean the read-only media? ... Or, did you mean by
> 'removable media' something else than 'readonly media' ?
I think this could also be some writable memory stick that a
maintainer uses in order to have always her/his own environment. If
(g)vim is started from there but reads the environment variables
defined by the owner of the machine then the wrong configuration und
plugin files are used (in the eyes of the maintainer).
The problem can be generalized and have, in my opinion, nothing to
do with removable media, but with the use of multiple versions and
environments by one and the same user. E.g. a beta tester may use a
vim version that is still in development and test different
configurations, also different system configurations. But for
productive work she/he uses a stable version of vim with
corresponding configuration and plugin files.
I think this problems can already be solved now by means of the -u,
-U, and eventually the -i option and by defining the 'runtimepath'
within the vimrc file explicitly.
But when the idea with the new environment variables as stated above
will be implemented, then, as I mentioned above, it would make sense
to introduce a new commando line option to explicitly override any