From: Apoorv via Guix-patches via <guix-patches@gnu.org>
To: 69623@debbugs.gnu.org
Subject: [bug#69623] Update emacs-evil-collection to 0.0.10
Date: Fri, 8 Mar 2024 04:10:56 +0100 (CET) [thread overview]
Message-ID: <NsR1hLA--3-9@tuta.io> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 455 bytes --]
evil-mode was causing issues because of corfu. Looking around it seems like the issue is because of some change in evil-collection, which in Guix ATM is pretty outdated. So I created this issue on their repo, https://github.com/emacs-evil/evil-collection/issues/786
and they have a new tag up now, I created this patch to update emacs-evil-collection package to the latest tag now.
--
Sent with Tuta; enjoy secure & ad-free emails:
https://tuta.com
[-- Attachment #1.2: Type: text/html, Size: 1165 bytes --]
[-- Attachment #2: update_emacs_evil_collection_0_0_10.patch --]
[-- Type: text/x-patch, Size: 786 bytes --]
diff --git a/gnu/packages/emacs-xyz.scm b/gnu/packages/emacs-xyz.scm
index 7fa5df9202..4093af9747 100644
--- a/gnu/packages/emacs-xyz.scm
+++ b/gnu/packages/emacs-xyz.scm
@@ -16298,7 +16298,7 @@ (define-public emacs-evil
(define-public emacs-evil-collection
(package
(name "emacs-evil-collection")
- (version "0.0.9")
+ (version "0.0.10")
(source
(origin
(method git-fetch)
@@ -16307,7 +16307,7 @@ (define-public emacs-evil-collection
(commit version)))
(file-name (git-file-name name version))
(sha256
- (base32 "1y1ig4shqaaiiwqm5pv8hvh8ynr6irhffkgmpyzmhdaaicxnfazc"))))
+ (base32 "09hnxb8nh3g0hi93fz9f1y164gv9iyh5994wfn6fsq2v1xdz8phm"))))
(build-system emacs-build-system)
(arguments
(list
next reply other threads:[~2024-03-08 3:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-08 3:10 Apoorv via Guix-patches via [this message]
2024-03-09 12:40 ` [bug#69623] Update emacs-evil-collection to 0.0.10 ziyed mstph
2024-03-10 4:05 ` Apoorv via Guix-patches via
2024-03-19 20:12 ` Jelle Licht
2024-03-20 2:25 ` [bug#69623] [PATCH] " Apoorv via Guix-patches via
2024-03-20 17:45 ` Christopher Baines
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=NsR1hLA--3-9@tuta.io \
--to=guix-patches@gnu.org \
--cc=69623@debbugs.gnu.org \
--cc=apoorvs@tuta.io \
/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).