From: HiPhish <hiphish@posteo.de>
To: 35680@debbugs.gnu.org
Subject: [bug#35680] [PATCH] Update Neovim to version 0.3.5
Date: Sat, 11 May 2019 00:01:51 +0200 [thread overview]
Message-ID: <4725920.dTlGXAFRqV@aleksandar-ixtreme-m5740> (raw)
[-- Attachment #1: Type: text/plain, Size: 296 bytes --]
This patch updates Neovim to the current version. As a side note, there is a
TODO from the previous definition to remove an in-place patching when the
package definition gets updated; the fix is not in 0.3.5, so I have not removed
this part of the defintion on purpose, it is not an oversight.
[-- Attachment #2: 0001-gnu-packages-vim.scm-neovim-Update-to-v0.3.5.patch --]
[-- Type: text/x-patch, Size: 1055 bytes --]
From 2f68bfe42593dfd03338c76c6a0b9ea8eb217fc1 Mon Sep 17 00:00:00 2001
From: HiPhish <hiphish@posteo.de>
Date: Fri, 10 May 2019 23:36:47 +0200
Subject: [PATCH] * gnu/packages/vim.scm (neovim): Update to v0.3.5.
---
gnu/packages/vim.scm | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gnu/packages/vim.scm b/gnu/packages/vim.scm
index dadffa3ab1..b2fd6cac99 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -729,7 +729,7 @@ are detected, the user is notified.")))
(define-public neovim
(package
(name "neovim")
- (version "0.3.4")
+ (version "0.3.5")
(source
(origin
(method url-fetch)
@@ -738,7 +738,7 @@ are detected, the user is notified.")))
(file-name (string-append name "-" version ".tar.gz"))
(sha256
(base32
- "03mwfhr9rq86p8lypbdfyl7c7xyn6nzv2ipd8jc33bxzvs5i0hd6"))))
+ "1min68r4rnyfly9j86szkx7gkj4924vbc74hg17j2crijr1h1cxq"))))
(build-system cmake-build-system)
(arguments
`(#:modules ((srfi srfi-26)
--
2.19.1
next reply other threads:[~2019-05-10 22:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 22:01 HiPhish [this message]
2019-05-11 7:33 ` bug#35680: [PATCH] Update Neovim to version 0.3.5 Arun Isaac
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=4725920.dTlGXAFRqV@aleksandar-ixtreme-m5740 \
--to=hiphish@posteo.de \
--cc=35680@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.