On 23/04/08 00:20, Meikel Brandmeyer wrote:
[...]
> I think of distribution not only of some batteries-included vim package,
> but also some system-installation. I worked as a system administrator
> during my study time and was responsible for 40 public dialog stations,
> where the students of our faculty could work. I consider it good
> practice to provide the users a comfortable system. If the first thing,
> they have to do, is to start installing software in their home
> directory, I did something wrong. So I'd also like to preinstall some
> of the more popular plugins.
[...]
The problem is: the user might have more than he wants. I like the way
the matchit plugin is distributed: present but not active, so the only
thing necessary to make it work (while still benefiting from future
upgrades if any) is a $VIM/vimfiles/plugin/matchit.vim consisting of the
one line
runtime macros/matchit.vim
For the help, it's harder to do it on Windows, but on Unix a softlink
from $VIM/vimfiles/doc/matchit.txt pointing to
../../vim71/macros/matchit.txt does the trick. (For the plugin itself,
the advantage of _not_ using a softlink is that (a) it works even on
Windows and (b) if you have several Vim versions installed, each of them
will use its own version of the plugin, thus sidetracking any
compatibility issues.)
Of course, it would be even easier with a "Preferences" popup menu
including a Plug-ins tab with a set of checkboxes:
_Plug-ins to be loaded at startup______________________
[x] matchit
[ ] getscriptPlugin
[x] gzip
[x] matchparen
[x] netrwPlugin
[x] rrhelper
[ ] spellfile
[x] tarPlugin
[x] tohtml
[x] vimballPlugin
[x] zipPlugin
[x] syntaxcomplete
[x] zzsplash
including a couple I wrote myself; but, also "of course", that kind of
menu isn't "the Vim way to do it" (and BTW, IMHO a vimrc is more
powerful than any closed set of Preferences). I believe it would be
possible to implement it though (or something similar), with no change
to the existing plugins, by means of 'noloadplugins' and as many lines
(maybe ":runtime" lines at the end of the vimrc, or rather in a separate
script called from the vimrc, to make it easier to change settings) as
there are plugins to be loaded.
You might want to save the initial status of &lpl in order to avoid
loading _any_ plugins when run with either -u NONE or --noplugin on the
command-line.
Best regards,
Tony.
--
Giving up on assembly language was the apple in our Garden of Eden:
Languages whose use squanders machine cycles are sinful. The LISP
machine now permits LISP programmers to abandon bra and fig-leaf.
-- Epigrams in Programming, ACM SIGPLAN Sept. 1982
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
