Handling subdirectories about minpac HOT 13 CLOSED

Sorry for being late.
I implemented this in the devel branch. (#97)

from minpac.

I also want this feature. https://github.com/l04m33/vlime needs a subdirectory for the rtp.

from minpac.

@k-takata I'd be willing to help add in the ability to set the runtimepath similar to how vim-Plug does it (mentioned here: #33 (comment)). Are you actively working on this? Or is this in progress in any way?

from minpac.

vim-plug has an rtp option which is useful in this scenario. e.g. you can use:

Plug 'nsf/gocode', { 'rtp': 'vim' }

That will check out the entire nsf/gocode repository, then set Vim's runtimepath to include the vim directory within that repository. I'm guessing that this approach won't work here, since minpac doesn't manage Vim's runtimepath.

To make this work for minpac, I think it would be necessary to only checkout the vim subdirectory of the repository. Apparently Git can do this using sparse checkouts.

from minpac.

Hmm, does sparse checkout strip directory structure?
I think it checks out only specified files/directories but the directory structure is kept.

One possible workaround is using another package and create a symlink in it.

mkdir -p ~/.vim/pack/bundle/start
cd ~/.vim/pack
ln -s minpac/start/gocode/vim bundle/start/gocode

(not tested)

from minpac.

You're right about sparse checkout: it does maintain the directory structure of the original repo. My mistake!

The symlink idea makes sense. I suppose you could get away with putting both the full repository and the symlink in the same package? e.g.:

cd ~/.vim/pack/minpac/start
git clone https://github.com/nsf/gocode.git gocode-full
ln -s gocode-full/vim gocode

Here, I'm using gocode-full as the name of the full repository, and gocode as the name for the symlink to the vim subdirectory within.

from minpac.

In that case, minpac#clean() will remove gocode.

from minpac.

Oh yeah, I hadn't thought of that.

I was wondering whether you might consider adding an option to minpac#add() so that you could do something like this?

call minpac#add('nsf/gocode', { 'subdir': 'vim' })

I'm not sure if subdir is the right choice of name for that key, but you get the idea. (The rtp option used by vim-plug and vundle would be a misnomer here) If a plugin is registered with this option, it would become a special case when running minpac#update() (and potentially also when running minpac#clean()).

Is it worth adding all of that extra code just to handle these special cases? I'm not sure, especially since examples like sonph/onehalf and nsf/gocode are uncommon. Alternatively, it might be worthwhile adding something to the documentation to describe how to install these kinds of plugin using minpac. If that's your preferred option, I can help.

from minpac.

Just run into this with both nginx and docker repos

from minpac.

Isn't it possible to only change the dir to clone into to a special dir for "full" repos, and then just symlink the dir option value.

mkdir -p ~/.vim/pack/minpac/full
cd ~/.vim/pack/minpac/full
git clone https://github.com/nsf/gocode.git
cd ~/.vim/pack/minpac/start
ln -s ../full/gocode gocode

from minpac.

google/yapf is another example where the vim plugin is in a subdir

from minpac.

I too am having the same issue with https://github.com/l04m33/vlime.

from minpac.

Thanks for this @k-takata

from minpac.