From: Foo Chuan Wei <chuanwei.foo@hotmail.com>
To: 51156@debbugs.gnu.org
Subject: [bug#51156] [PATCH] gnu: Add vim-paredit
Date: Tue, 12 Oct 2021 12:59:11 +0000 [thread overview]
Message-ID: <PU1PR01MB21559EBAA7CA42951D75EB3C8DB69@PU1PR01MB2155.apcprd01.prod.exchangelabs.com> (raw)
* gnu/packages/vim.scm (vim-paredit): New variable.
---
gnu/packages/vim.scm | 27 +++++++++++++++++++++++++++
1 file changed, 27 insertions(+)
diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
index 92189b7094..ab04db9105 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -1069,3 +1069,30 @@ 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-paredit
+ (let ((commit "97d51d099523b37bb35cbcf3564cbfb46e66e4ec")
+ (revision "1"))
+ (package
+ (name "vim-paredit")
+ (version (git-version "0.0.0" revision commit))
+ (source
+ (origin
+ (method git-fetch)
+ (uri (git-reference
+ (url "https://github.com/kovisoft/paredit")
+ (commit commit)))
+ (file-name (git-file-name name version))
+ (sha256
+ (base32 "07d5s20r0ssd7rir45vy0fqlci44gha1a81rcilgar227f3nw328"))))
+ (build-system copy-build-system)
+ (arguments
+ '(#:install-plan
+ '(("doc" "share/vim/vimfiles/")
+ ("plugin" "share/vim/vimfiles/"))))
+ (home-page "https://github.com/kovisoft/paredit")
+ (synopsis "Vim plugin for structured editing of Lisp S-expressions")
+ (description
+ "Paredit performs structured editing of Lisp S-expressions in Vim.
+Paredit.vim is similar to paredit.el for Emacs.")
+ (license license:public-domain))))
base-commit: 35aaf1fe10488ae9ed732fb2c383d09a70c109c0
--
2.25.1
next reply other threads:[~2021-10-12 13:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-12 12:59 Foo Chuan Wei [this message]
2021-10-13 9:54 ` bug#51156: [PATCH] gnu: Add vim-paredit 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=PU1PR01MB21559EBAA7CA42951D75EB3C8DB69@PU1PR01MB2155.apcprd01.prod.exchangelabs.com \
--to=chuanwei.foo@hotmail.com \
--cc=51156@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 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).