From: Jack Hill <jackhill@jackhill.us>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org
Subject: Re: Neovim plugin/addon packaging
Date: Sat, 1 May 2021 16:25:18 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2105011456310.2109@marsh.hcoop.net> (raw)
In-Reply-To: <YIv1ueUN+CdVuYbC@3900XT>
[-- Attachment #1: Type: text/plain, Size: 2968 bytes --]
Thanks for your reply.
On Fri, 30 Apr 2021, Efraim Flashner wrote:
> On Fri, Apr 30, 2021 at 01:03:23AM -0400, Jack Hill wrote:
>> Greetings Guix,
>>
>> I'd like to improve the experience of installing Neovim plugins/add-ons with
>> Guix. I've submitted #48112 [0] which adds an XDG_DATA_DIRS search path so
>> nvim (the Neovim executable name) will be able to find plugins installed by
>> guix at …/share/nvim/site.
>
> I guess my first question is does it work? I think I first tried
> something similar for vim with 'share/vim/vimfiles' but it didn't
> actually work for vim.
Yes, it does work! I tested it with neovim-syntastic and a local
neovim-fugitive package both with a guix environment and manually
manipulated environment variables.
A difference between Neovim and Vim is that Neovim supports XDG_DATA_DIRS
(and XDG_CONFIG_DIRS) as real search paths while the environment variables
for Vim are single directories (compare `:help runtimepath` in the two
editors).
>> Currently, we only have one such package, neovim-syntastic. I'd like to add
>> more. Many plugins are compatible with both vim and nvim. However, they
>> search for plugins at different paths. Therefore, the vim-syntastic and
>> neovim-syntastic packages, which use the copy-build-system, differ only in
>> the destination directories of the install-plan (and changing "Vim" to
>> "Neovim" in the description).
>>
>> My initial inclination is to remove the duplication of maintaining two
>> install-plans (and other arguments) by creating a procedure that would take
>> as input a Vim package that uses copy-build-system and output a Neovim
>> package with the install-plan re-written.
>>
>> Perhaps that solution would be overwrought. How would you recommend handling
>> this situation?
>
> My first idea would be to have the one package install the files into
> both directories and combine them, but I feel like it falls apart when
> it comes to searching for vim/neovim plugins and naming. One package
> with two names? Call it vim-neovim-syntastic?
>
> If vim/neovim move more apart and actually need separate plugins in the
> future then I guess it would make more sense to have two actual packages
> that can be installed by name (vim-foo and neovim-foo).
A combined package is an interesting suggestion. However, I share the
concern about searching for packages. Having packages that are compatible
with both editors use one naming scheme and ones that are compatible with
only one use a different naming scheme seems like a implementation detail
that would be better not to expose to me.
I drew inspiration for creating the Neovim package variants with a
procedure from the package-for-python2 and sbcl-package->ecl-package. Of
course those procedures have build system support and aren't depending on
a common usage pattern of copy-build-system.
Is it time a a vim-build-system? Perhaps not, but I'm still not sure what
the right way forward is.
Best,
Jack
next prev parent reply other threads:[~2021-05-01 20:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 5:03 Neovim plugin/addon packaging Jack Hill
2021-04-30 12:19 ` Efraim Flashner
2021-05-01 20:25 ` Jack Hill [this message]
2021-05-02 9:19 ` Efraim Flashner
2021-05-03 4:46 ` Jack Hill
2021-05-03 5:46 ` Efraim Flashner
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=alpine.DEB.2.21.2105011456310.2109@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).