From: Cecilio Pardo <cpardo@imayhem.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: luangruo@yahoo.com, 74423@debbugs.gnu.org, Eli Zaretskii <eliz@gnu.org>
Subject: bug#74423: Low level key events
Date: Thu, 26 Dec 2024 11:16:11 +0100 [thread overview]
Message-ID: <b3e7839a-3fac-49e4-a507-fc34f6a71aa4@imayhem.com> (raw)
In-Reply-To: <jwvseqgbd1y.fsf-monnier+emacs@gnu.org>
On 22/12/2024 5:31, Stefan Monnier wrote:
> I'm not expert in the C level part of that code, so I provide
> feedback below only for the Lisp-facing part.
Thanks a lot for the review. I'm working on it.
> Maybe instead of focusing on running a command, `llk-handle` and
> `llk-bind` should concentrate on generating "normal" events that are
> then looked up in the normal keymaps.
>
> So the user would use them only to specify which events should be
> recognized and which should be ignored. Then the user can use the
> standard keymaps to declare what to do in response to `double-xk-shift-l`.
> WDYT?
Yes, I think that's better. I did it the other way to keep it as
separate as possible from normal events, as some people thought this was
a bad idea.
How can we make sure that only the user configures this, and external
packages do not?
next prev parent reply other threads:[~2024-12-26 10:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fb50ec11-7aec-481e-8a3a-ecdcf22eb7c0@imayhem.com>
[not found] ` <31bdc55d-8c13-4de0-9cef-bd6cc4fb033f@imayhem.com>
[not found] ` <s1r8qtzsvbe.fsf@yahoo.com>
2024-11-18 20:35 ` bug#74423: Low level key events Cecilio Pardo
2024-11-18 23:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-23 12:08 ` Cecilio Pardo
2024-11-19 15:29 ` Eli Zaretskii
2024-11-19 16:43 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-11-19 20:05 ` Cecilio Pardo
2024-11-20 4:21 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-02 16:54 ` Cecilio Pardo
2024-12-04 20:01 ` Eli Zaretskii
2024-12-04 21:25 ` Cecilio Pardo
2024-12-05 5:41 ` Eli Zaretskii
2024-12-06 1:01 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-07 21:52 ` Cecilio Pardo
2024-12-13 22:55 ` Cecilio Pardo
2024-12-14 1:16 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-14 9:26 ` Cecilio Pardo
2024-12-14 11:14 ` Eli Zaretskii
2024-12-18 10:59 ` Cecilio Pardo
2024-12-22 4:31 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-26 10:16 ` Cecilio Pardo [this message]
2024-12-26 14:54 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=b3e7839a-3fac-49e4-a507-fc34f6a71aa4@imayhem.com \
--to=cpardo@imayhem.com \
--cc=74423@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=luangruo@yahoo.com \
--cc=monnier@iro.umontreal.ca \
/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).