Re: Packages and plugin's subdirectories

Nicola wrote:

> On 2016-03-30 04:43:56 +0000, Nicola said:
> >
> > If that is the intended behaviour, maybe it should be noted more explicitly
> > in the help files. In `:h packages`, it is written that Vim:
>
> Also note this difference: if pack/foo/opt/neocomplete is loaded during a
> session with `:packadd neocomplete`, only one file is sourced, because only
> the package mechanism kicks in. But `packadd! neocomplete` is put in .vimrc,
> then all files are sourced, because that adds the path to runtimepath before
> the plugin loading phase kicks in.

Good point, we don't want this to work differently.

--
If Apple would build a car...
... it would be powered by the sun, be reliable, five times
as fast and twice as easy to drive; but would only run on
five percent of the roads.

/// Bram Moolenaar -- Bram@Moolenaar.net -- 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_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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.