On Thu, Mar 03, 2016 at 05:55:25PM +0100, Bram Moolenaar wrote:
>
> Hirohito Higashi wrote:
>
> > Why is it different in the search pattern at 'runtimepath' and 'packpath' ?
> >
> > 'runtimepath': "plugin/**/*.vim" (in main.c: 633)
> > 'packpath': "plugin/*.vim" (in source_packages())
> >
> > Is this expected?
> > There is no *.vim directly under plugin in the existing plug-in, which
> > is under the subfolder is not able to operate in 'packpath'.
> >
> > e.g. https://github.com/sgur/vim-textobj-parameter
>
> Yes, this is intentional.
So, we can't just take an addon that worked when you unzipped it
directly into ~/.vim and instead unzip it into ~/.vim/pack/<addon>/ever?
Why?
I understand the additional directory level that's being imposed ("ever"
and "opt"), even though that seems like added complexity to the user for
little gain in the common case. However, I don't see why an addon
author may now need to choose between structuring their repo so that it
works with existing plugin managers or so that it works with 'packpath'.
Shouldn't the rules for how things are sourced be the same, regardless
of whether it's the runtime directories in ~/.vim or the runtime
directories in ~/.vim/pack/<addon>/ever?
Cheers,
--
James
GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <[email protected]>
--
--
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.
