From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "gyara" <me@gyara.moe>, <57456@debbugs.gnu.org>
Subject: [bug#57456] [PATCH] gnu: Add neovim-packer.
Date: Sun, 28 Aug 2022 08:38:08 +0100 [thread overview]
Message-ID: <CMHHNZ2ST28P.2EZMHIZLY2YOM@guix-aspire> (raw)
In-Reply-To: <6cd04239206a8a85b0d20ec5a5904b071d800b53.1661660180.git.me@gyara.moe>
Hello!
On Sun Aug 28, 2022 at 5:16 AM BST, gyara via Guix-patches via wrote:
> + (let ((commit "3a9f9801f683946b9f1047d8f4bf9946c29e927d")
> + (revision "1"))
Change to `0`, since this is the first revision in Guix.
> + (package
> + (name "neovim-packer")
> + (version (git-version "0.0.0" revision commit))
> + (home-page "https://github.com/wbthomason/packer.nvim")
Move this above `synopsis`.
> + (uri (git-reference
> + (url "https://github.com/wbthomason/packer.nvim.git")
Remove the `.git` part.
> + (arguments
> + '(#:install-plan '(("lua"
> + "share/nvim/site/pack/packer/start/packer.nvim/")
> + ("doc"
> + "share/nvim/site/pack/packer/start/packer.nvim/"))))
Probably better formatting:
(arguments
(list #:install-plan
#~'(("doc" "share/nvim/site/pack/guix/start/packer/")
("lua" "share/nvim/site/pack/guix/start/packer/"))))
(I used site/guix instead of site/packer for my own Guix
neovim packages; it seems like any name after site/ works.)
> + (synopsis "Neovim Plugin manager")
This might be better as:
Plugin manager for Neovim
> + (description
> + "A use-package inspired plugin manager for Neovim. Uses native packages,
> + supports Luarocks dependencies, written in Lua, allows for expressive config")
And this as:
This package provides a plugin manager for Neovim, inspired by Emacs's
@code{euse-package}. It's written in Lua, supports Luarocks dependencies,
and is based on Vim's builtin plugin support.
-- (
next prev parent reply other threads:[~2022-08-28 7:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-28 4:16 [bug#57456] [PATCH] gnu: Add neovim-packer gyara via Guix-patches via
2022-08-28 7:38 ` ( via Guix-patches via [this message]
2022-08-28 8:21 ` ギャラ via Guix-patches via
2022-08-28 8:21 ` [bug#57456] [PATCH v2] " gyara via Guix-patches via
2022-08-28 8:25 ` ( via Guix-patches via
2022-08-28 9:11 ` [bug#57456] [PATCH v3] " gyara via Guix-patches via
2022-08-28 9:16 ` ( via Guix-patches via
2022-08-29 4:01 ` [bug#57456] Packer.nvim hard code its name ギャラ via Guix-patches via
2022-08-29 4:01 ` [bug#57456] [PATCH v4] gnu: Add neovim-packer gyara via Guix-patches via
2022-09-06 14:32 ` bug#57456: [PATCH] " Ludovic Courtès
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=CMHHNZ2ST28P.2EZMHIZLY2YOM@guix-aspire \
--to=guix-patches@gnu.org \
--cc=57456@debbugs.gnu.org \
--cc=me@gyara.moe \
--cc=paren@disroot.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).