From: SeerLite <seerlite@disroot.org>
To: nils@promisedlandt.de
Cc: Efraim Flashner <efraim@flashner.co.il>, help-guix@gnu.org
Subject: Re: Generating helptags for vim plugins
Date: Wed, 22 Feb 2023 21:28:45 +0100 [thread overview]
Message-ID: <171ce6c5a88fcf457099f68031a23e40@disroot.org> (raw)
In-Reply-To: <291541103.381025.1676975528001@office.mailbox.org>
On 2023-02-21 11:32, nils@promisedlandt.de wrote:
> I also think that having each plugin in its own folder is the most
> robust solution. Both vim and neovim have package loading that works
> with no or minimal configuration for quite a few years now, and to me
> it makes sense if guix adds the plugins in the structure the built-in
> loaders expect.
> However, I would not expect the user to have to :packadd each plugin
> separately. Having plugins autoload is the behaviour with the current
> guix packages, and I think that's the most common use case anyway.
> For that, I think all that needs to be done is to install the plugins
> at ~/.guix-home/profile/share/vim/plugins/pack/guix/start/<plugin_name>
> and then having set packpath=~/.guix-home/profile/share/vim/plugins in
> the system vimrc.
>
> For neovim plugins, the path would be
> ~/.guix-home/profile/share/nvim/site/pack/guix/start/<plugin_name>.
Hi! Whichever way you go I recommend you avoid hardcoded paths and
instead use search paths. This way you can have Vim and its plugins in a
non-default profile and no collisions or unexpected sourcing will happen
in `guix shell`. `--pure` should be pure!
See my old patch for more info: <https://issues.guix.gnu.org/54221#30>
SeerLite
prev parent reply other threads:[~2023-02-23 8:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-19 10:09 Generating helptags for vim plugins nils
2023-02-19 20:06 ` Efraim Flashner
2023-02-21 10:32 ` nils
2023-02-22 20:28 ` SeerLite [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=171ce6c5a88fcf457099f68031a23e40@disroot.org \
--to=seerlite@disroot.org \
--cc=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=nils@promisedlandt.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).