From: Ihor Radchenko <yantar92@posteo.net>
To: Psionic K <psionik@positron.solutions>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Delegating user-reserved key binding space definition to users
Date: Fri, 25 Nov 2022 03:31:17 +0000 [thread overview]
Message-ID: <87zgcfaewq.fsf@localhost> (raw)
In-Reply-To: <CADQMGATUUz6pNjQNobgfx+K98zZ_swy_OuJ8-NKVWTZGVOMQDw@mail.gmail.com>
Psionic K <psionik@positron.solutions> writes:
> Abstract commands are just command remap targets in the global map. The
> concrete global commands would directly command remap in the global map.
> Abstract command bindings would be consumed when modes generate keymaps for
> major & minor modes. A Corfu map generator would for example see an
> abstract command like "user-next" bound with the C-n sequence and choose to
> shadow C-n in its map. If the user rebinds the global abstract command,
> the other modes could easily follow this change, perhaps even though a hook
> to immediately propagate the change.
+1
Anyone who tried to re-bind default bindings for, say, C-n/C-p/n/p might
be familiar what the problem with current Emacs approach is. It is very
annoying to keep tweaking every single package bindings out there and
also deal with cascading key collisions.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2022-11-25 3:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 14:40 Delegating user-reserved key binding space definition to users Psionic K
2022-11-21 19:37 ` Stefan Monnier
2022-11-22 2:07 ` Phil Sainty
2022-11-25 2:48 ` Psionic K
2022-11-25 3:31 ` Ihor Radchenko [this message]
2022-11-25 13:53 ` xenodasein--- via Emacs development discussions.
2022-11-25 15:16 ` Stefan Monnier
2022-11-26 6:44 ` Ihor Radchenko
2022-11-26 17:29 ` Stefan Monnier
2022-11-27 5:45 ` Ihor Radchenko
2022-11-27 11:26 ` Psionic K
2022-11-27 11:53 ` Psionic K
2022-11-28 18:15 ` Stefan Monnier
2022-11-28 18:37 ` Eli Zaretskii
2022-11-29 2:38 ` Psionic K
2022-11-29 4:01 ` Stefan Monnier
2022-11-29 5:22 ` Psionic K
2022-11-29 13:03 ` Eli Zaretskii
2022-11-30 6:23 ` Psionic K
2022-11-30 9:01 ` xenodasein--- via Emacs development discussions.
2022-11-30 13:44 ` Eli Zaretskii
2022-11-29 11:54 ` John Yates
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=87zgcfaewq.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-devel@gnu.org \
--cc=psionik@positron.solutions \
/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).