Tyru wrote:
> On Tue, Feb 9, 2016 at 7:03 PM, Bram Moolenaar <[email protected]> wrote:
> >
> > I had another idea. Currently when installing a plugin or support for
> > a language, the files are scattered over different directories under
> > $VIMRUNTIME. That makes it hard to update them.
> >
> > How about this: use $VIMRUNTIME/bundles. Below that will be the
> > directories that are usually directly under $VIMRUNTIME. For example,
> > netrw would be installed in the directories:
> > $VIMRUNTIME/bundles/netrw/plugin
> > $VIMRUNTIME/bundles/netrw/autoload
> > $VIMRUNTIME/bundles/netrw/syntax
> > It doesn't need an "indent" directory.
>
> It sounds very interesting and helpful! :)
> if a runtime directory is in hand of users.
>
> But there are 3 problems for runtime bundle directory:
>
> 1. Runtime plugin must specify the least supported version of Vim
>
> If Vim is too old, required functions for a runtime plugin may not
> exist (e.g. shiftwidth()).
That is unrelated to how plugins are organized, the plugin needs to
check for the Vim version and features anyway. E.g. if a plugin
requires Python and there is no Python it can finish.
> 2. Need to separate *.vim files into directories, but how should we
> separate them?
>
> How can we say *.vim files are "related" in a same directory?
> How should we determine the rule?
I don't understand the question. If you get a plugin, either from
github, a .zip file or whatever, you have the files that go into one
directory.
> > That way the directory can be put under version control or updated in
> > any other way easily. E.g. unpacking a zip archive that you get from
> > Charles's site. And it's also easy to get rid of: delete the directory
> > below bundles. No need to hunt down the files that you unpacked before.
>
> 3. How should we setup a runtime directory?
>
> Normally, $VIMRUNTIME is under $VIM and it is often unwritable
> (especially in has('unix') environment).
>
> Are you thinking that users define $VIMRUNTIME and
> copy a runtime directory / make a new runtime directory by himself for
> current Vim?
I was using $VIMRUNTIME as "whatever runtime directory you use". For
Unix it would go under ~/.vim/bundles/... (or whatever name we end up
using for "bundles"). If you are a sysadmin and you want to make the
plugin available for all users you put it under /usr/local/share/
somewhere.
[...]
--
Some of the well known MS-Windows errors:
EMEMORY Memory error caused by..., eh...
ELICENSE Your license has expired, give us more money!
EMOUSE Mouse moved, reinstall Windows
EILLEGAL Illegal error, you are not allowed to see this
EVIRUS Undetectable virus found
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
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/d/optout.
