From: Jack Hill <jackhill@jackhill.us>
To: guix-devel@gnu.org
Subject: Neovim plugin/addon packaging
Date: Fri, 30 Apr 2021 01:03:23 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2104300042140.2109@marsh.hcoop.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1088 bytes --]
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.
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?
[0] https://issues.guix.gnu.org/48112
Best,
Jack
next reply other threads:[~2021-04-30 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-30 5:03 Jack Hill [this message]
2021-04-30 12:19 ` Neovim plugin/addon packaging Efraim Flashner
2021-05-01 20:25 ` Jack Hill
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
* 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.2104300042140.2109@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.