all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "\( via Guix-patches" via <guix-patches@gnu.org>
To: "gyara" <me@gyara.moe>, <57456@debbugs.gnu.org>
Subject: [bug#57456] [PATCH v2] gnu: Add neovim-packer.
Date: Sun, 28 Aug 2022 09:25:49 +0100	[thread overview]
Message-ID: <CMHIOHFFGYLJ.31L9HJ167C8XU@guix-aspire> (raw)
In-Reply-To: <4d2f631d0a57d0ef06423068330554566435c4d0.1661674866.git.me@gyara.moe>

On Sun Aug 28, 2022 at 9:21 AM BST, gyara via Guix-patches via wrote:
> +      (arguments
> +       '(#:install-plan '(("lua" "share/nvim/site/pack/packer/start/packer/")
> +                          ("doc" "share/nvim/site/pack/packer/start/packer/"))))

Use

  (list #:install-plan
        #~'(...))

instead. Also, s'pack/packer'pack/guix' is probably a nicer place to install
Guix Neovim plugins.

> +      (description
> +       "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.")

typo: euse-package

    -- (




  reply	other threads:[~2022-08-28  8:57 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
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 [this message]
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CMHIOHFFGYLJ.31L9HJ167C8XU@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 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.