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: 58209@debbugs.gnu.org
Cc: ギャラ <me@gyara.moe>
Subject: [bug#58209] [PATCH 2/2] gnu: neovim: Update to 0.8.0.
Date: Sat,  1 Oct 2022 09:30:33 +0900	[thread overview]
Message-ID: <0f1b79a0cfc3f5eadbd52f5ec15051ff424eabdc.1664584231.git.me@gyara.moe> (raw)
In-Reply-To: <4dd7ac5cd47d6f0c936690b99a7416b990d89b99.1664584231.git.me@gyara.moe>

* gnu/packages/vim.scm (neovim): Update to 0.8.0.
---
 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 c6bfbb5c6b..901527e159 100644
--- a/gnu/packages/vim.scm
+++ b/gnu/packages/vim.scm
@@ -685,7 +685,7 @@ (define-public neovim-syntastic
 (define-public neovim
   (package
     (name "neovim")
-    (version "0.7.2")
+    (version "0.8.0")
     (source (origin
               (method git-fetch)
               (uri (git-reference
@@ -694,7 +694,7 @@ (define-public neovim
               (file-name (git-file-name name version))
               (sha256
                (base32
-                "1jn4i4ral79ys06i50bimylm515sfh41z503gj50a74h1ylg0z4w"))))
+                "0hkd49wkxfi6k1xa92hdd4b9z356r32hbpr78z1cigcln1wr0z7j"))))
     (build-system cmake-build-system)
     (arguments
      (list #:modules
-- 
2.37.3





  reply	other threads:[~2022-10-01  0:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-01  0:28 [bug#58209] [patch 0/2] gnu: neovim: Update to 0.8.0 ギャラ via Guix-patches via
2022-10-01  0:30 ` [bug#58209] [PATCH 1/2] gnu: libvterm: Update to 0.3.0 ギャラ via Guix-patches via
2022-10-01  0:30   ` ギャラ via Guix-patches via [this message]
2022-10-02 12:08 ` bug#58209: [patch 0/2] gnu: neovim: Update to 0.8.0 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=0f1b79a0cfc3f5eadbd52f5ec15051ff424eabdc.1664584231.git.me@gyara.moe \
    --to=guix-patches@gnu.org \
    --cc=58209@debbugs.gnu.org \
    --cc=me@gyara.moe \
    /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.