bug#25713: Mixed collecton of vim-plugins

[Kei Kebreau]

ng0 <address@hidden> writes:

> Hi,
>
> I have a collection of Vim plugins ready:
>
>       gnu: Add vim-neocomplete.
>       gnu: Add vim-scheme.
>       gnu: Add vim-neosnippet-snippets.
>       gnu: Add vim-neosnippet.
>       gnu: Add vim-luna.
>       gnu: Add vim-context-filetype.
>       gnu: Add vim-airline.
>       gnu: Add vim-airline-themes.
>       gnu: Add vim-orgmode.
>       gnu: Add vim-markdown.
>
> Only two of them need some fixes, but this should be doable tomorrow.
> Before I send them in tomorrow, I'd like to take the time to ask a question
> on a detail which is not obvious in the patches.
>
> I use them all by setting this in my .vimrc:
>
> " plugins handled by Guix:
> set rtp+=~/.guix-profile/share/vim/vimfiles/
>
> This is basically what Vundle does too, and it works for me.
>
> How is this best communicated to people installing these packages?
> This isn't an environment variable, so maybe simply put it in the
> documentation maybe?
>
> What do you think?
>
> Unrelated: The exception from the default seems to be that you have a
> Makefile. The default case is that you simply copy every folder to the
> path.
> In the future I can see my usage of the gnu build-system I used lead to
> vim-build-system which simplifies this process when I understand more of
> the Vim packages.
>
> I used the patches list with the intention to just send the series to
> this email - Combined patches and discussion.

All pushed to master (and vim-luna was cleaned up as you wished).

signature.asc
Description: PGP signature