From: "Sebastián Monía" <sebastian@sebasmonia.com>
To: Jim Porter <jporterbugs@gmail.com>
Cc: emacs-devel@gnu.org
Subject: Re: Interest in keymap-set + use-package (+ bind-key)?
Date: Thu, 14 Nov 2024 09:13:31 -0500 [thread overview]
Message-ID: <thqna5e17vjo.fsf@sebasmonia.com> (raw)
In-Reply-To: <348bdf40-6c00-2f42-4859-a56f40e28833@gmail.com> (Jim Porter's message of "Sun, 10 Nov 2024 19:03:28 -0800")
Jim Porter <jporterbugs@gmail.com> writes:
> Currently, use-package uses the "legacy" 'define-key' by way of the
> bind-key package. This trips me up sometimes, since the spellings of
> keys are slightly different between 'define-key' and the newer
> 'keymap-set' (I mostly run into this when remapping a command).
>
> Would there be any interest in adding support (somehow) to use-package
> for 'keymap-set' and friends? I'm open to options for the specifics
> here. For example, bind-key is also useful for providing
> 'describe-personal-keybindings'. Maybe we could enhance bind-key to
> optionally work more like 'keymap-set'? That could be with some new
> option, like 'bind-key-use-keymap-set', or some new function, like
> 'keymap-bind-key'[1].
>
> Any thoughts? If this is something others would like, I'd be happy to
> implement this.
>
> [1] This could use a better name, but this name should hopefully
> suffice for discussion purposes.
I just read the NEWS entry about keymap-set, so thanks for that.
And I would say yes, it would be nice if use-package worked just like
the newer functions do.
Wouldn't it make sense to have bind-key use that syntax going forward,
though? Maybe it can't be done without breaking existing code, and
that's why we would need a new keyword?
Regards,
Seb
--
Sebastián Monía
https://site.sebasmonia.com/
next prev parent reply other threads:[~2024-11-14 14:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 3:03 Interest in keymap-set + use-package (+ bind-key)? Jim Porter
2024-11-14 14:13 ` Sebastián Monía [this message]
2024-11-14 21:47 ` Jim Porter
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=thqna5e17vjo.fsf@sebasmonia.com \
--to=sebastian@sebasmonia.com \
--cc=emacs-devel@gnu.org \
--cc=jporterbugs@gmail.com \
/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/emacs.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).