From: Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org>
To: jgart <jgart@dismail.de>, 55786-done@debbugs.gnu.org
Cc: Maxime Devos <maximedevos@telenet.be>
Subject: bug#55786: [PATCH 1/2] gnu: Add emacs-bind-map.
Date: Sat, 04 Jun 2022 23:32:17 +0200 [thread overview]
Message-ID: <87y1ycgkan@nckx> (raw)
In-Reply-To: <72dac9a0ac25a556f1986299d31a6d6184b17a30.camel@telenet.be>
[-- Attachment #1: Type: text/plain, Size: 936 bytes --]
Hi,
The GPL was added thanks to jgart[0], so I've pushed both of these
patches.
Maxime Devos 写道:
> Both of these result in a 404 for me.
https://github.com/justbur/emacs-bind-map (with extra ‘emacs-’)
works for me.
I changed the base version of emacs-bind-map to 1.1.2 as the
commit we use postdates [1].
My guess is an incomplete copy-paste job led to both?
…or maybe not, since spaceleader states its version as 0.0.3. I
don't see where either 0.2 came from.
I took the liberty of moving both lonely source hash strings up a
line, because I can :o)
I also re-indented the packages and expanded the description of
emacs-spaceleader just a bit, based on the .el comment and our own
emacs-evil-leader package.
Thanks!
T G-R
[0]: https://github.com/mohkale/spaceleader/issues/3
[1]:
https://github.com/justbur/emacs-bind-map/commit/6977e0fec5c4a3c62a10503798c2a15194167046
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 247 bytes --]
prev parent reply other threads:[~2022-06-04 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-03 19:16 [bug#55786] [PATCH 0/1] Add emacs-spaceleader jgart via Guix-patches via
2022-06-03 19:21 ` [bug#55786] [PATCH 1/2] gnu: Add emacs-bind-map jgart via Guix-patches via
2022-06-03 19:21 ` [bug#55786] [PATCH 2/2] gnu: Add emacs-spaceleader jgart via Guix-patches via
2022-06-03 19:43 ` Maxime Devos
2022-06-03 19:41 ` [bug#55786] [PATCH 1/2] gnu: Add emacs-bind-map Maxime Devos
2022-06-04 21:32 ` Tobias Geerinckx-Rice via Guix-patches via [this message]
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=87y1ycgkan@nckx \
--to=guix-patches@gnu.org \
--cc=55786-done@debbugs.gnu.org \
--cc=jgart@dismail.de \
--cc=maximedevos@telenet.be \
--cc=me@tobias.gr \
/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.