From: Efraim Flashner <efraim@flashner.co.il>
To: 51159@debbugs.gnu.org
Subject: [bug#51159] [PATCH] gnu: Add vim-nerdcommenter
Date: Mon, 25 Oct 2021 10:03:20 +0300 [thread overview]
Message-ID: <YXZWuOZrsuuN/jhO@3900XT> (raw)
In-Reply-To: <PU1PR01MB21554E125A15BDCFAABBF9148DB69@PU1PR01MB2155.apcprd01.prod.exchangelabs.com>
[-- Attachment #1: Type: text/plain, Size: 2264 bytes --]
I see that the latest tag is several years old and there has been
continued development since then. Does it make sense to package a newer
commit?
Also, if you add all the patches to the bottom of the file then they all
conflict with each other and it makes it harder to apply them.
On Tue, Oct 12, 2021 at 02:13:20PM +0000, Foo Chuan Wei wrote:
> * gnu/packages/vim.scm (vim-nerdcommenter): New variable.
> ---
> gnu/packages/vim.scm | 26 ++++++++++++++++++++++++++
> 1 file changed, 26 insertions(+)
>
> diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
> index 92189b7094..f668aa0867 100644
> --- a/gnu/packages/vim.scm
> +++ b/gnu/packages/vim.scm
> @@ -1069,3 +1069,29 @@ your code every time you make a change. @code{Vim-slime} is an attempt at
> getting some of these features into Vim. It works with any REPL and isn't tied
> to Lisp.")
> (license license:expat))))
> +
> +(define-public vim-nerdcommenter
> + (package
> + (name "vim-nerdcommenter")
> + (version "2.5.2")
> + (source
> + (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/preservim/nerdcommenter")
> + (commit version)))
> + (file-name (git-file-name name version))
> + (sha256
> + (base32 "0s862kzhvv9qpr7gxd3h52hczjvm55zyff5qn0z5095072pr3wjx"))))
> + (build-system copy-build-system)
> + (arguments
> + '(#:install-plan
> + '(("doc" "share/vim/vimfiles/")
> + ("plugin" "share/vim/vimfiles/"))))
> + (home-page "https://github.com/preservim/nerdcommenter")
> + (synopsis "Vim plugin for easy commenting of code")
> + (description
> + "NERD commenter is a Vim plugin that provides many different commenting
> +operations and styles which are invoked via key mappings and a menu. These
> +operations are available for most filetypes.")
> + (license license:cc0)))
>
> base-commit: 35aaf1fe10488ae9ed732fb2c383d09a70c109c0
> --
> 2.25.1
>
>
>
>
--
Efraim Flashner <efraim@flashner.co.il> רנשלפ םירפא
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-10-25 7:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 14:13 [bug#51159] [PATCH] gnu: Add vim-nerdcommenter Foo Chuan Wei
2021-10-25 7:03 ` Efraim Flashner [this message]
2021-11-01 4:53 ` [bug#51159] [PATCH v2] " Foo Chuan Wei
2021-11-04 13:33 ` bug#51159: " 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=YXZWuOZrsuuN/jhO@3900XT \
--to=efraim@flashner.co.il \
--cc=51159@debbugs.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.