unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: cpardo@imayhem.com, emacs-devel@gnu.org
Subject: Re: Physical keyboard events
Date: Mon, 04 Nov 2024 18:49:41 +0200	[thread overview]
Message-ID: <865xp3ueoq.fsf@gnu.org> (raw)
In-Reply-To: <877c9jjc93.fsf@yahoo.com> (message from Po Lu on Mon, 04 Nov 2024 22:37:44 +0800)

> From: Po Lu <luangruo@yahoo.com>
> Cc: cpardo@imayhem.com,  emacs-devel@gnu.org
> Date: Mon, 04 Nov 2024 22:37:44 +0800
> 
> Emacs already tries to establish a sensible relationship between
> modifier bits and Emacs modifiers, and clearly, the reasonable way
> forward is to write a small quantity of code to deduce the modifier bits
> produced by a keysym, and reuse the existing mechanism to report a
> modifier that users will expect, instead of engineering a different
> mechanism for the purposes of reporting modifier activation and
> deactivation, or, as Cecilio's patch currently does, reporting keysyms
> totally independent of the modifiers actually bound to their keys.

I can see a place for both.  It all depends on what the Lisp program
wants to do.  So I guess we should allow Lisp programs to receive one
or the other.

> >> BTW, if the intention is to forward just modifier key events to Lisp,
> >> don't let's refer to them as "physical keyboard events", but in more
> >> specific terms.
> >
> > Yes, I think the idea is to generate modifier key events and expose
> > them to Lisp.  What is more specific than "physical keyboard events"?
> 
> "Modifier activation and release events", perhaps?

That's a mouthful.  How about "low-level keyboard events"?



  reply	other threads:[~2024-11-04 16:49 UTC|newest]

Thread overview: 71+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-28 23:15 Physical keyboard events Cecilio Pardo
2024-10-29 13:40 ` Eli Zaretskii
2024-10-29 15:07   ` Cecilio Pardo
2024-10-29 15:38     ` Peter Feigl
2024-10-29 17:54       ` Cecilio Pardo
2024-10-29 23:41       ` James Thomas
2024-10-29 16:44     ` Eli Zaretskii
2024-10-29 16:55       ` Yuri Khan
2024-10-29 17:46         ` Eli Zaretskii
2024-10-30  2:56           ` Max Nikulin
2024-10-30  6:28             ` Yuri Khan
2024-10-30  6:39               ` Peter Feigl
2024-10-30 15:27               ` Eli Zaretskii
2024-10-30 17:13                 ` Yuri Khan
2024-10-30 17:37                   ` Eli Zaretskii
2024-10-30 19:26                     ` Dov Grobgeld
2024-10-30 19:36                       ` Juri Linkov
2024-10-30 19:55                       ` Eli Zaretskii
2024-10-31  6:13                     ` Yuri Khan
2024-10-30 15:21             ` Eli Zaretskii
2024-10-30 16:59               ` Max Nikulin
2024-10-29 17:56         ` Cecilio Pardo
2024-10-29 17:52       ` Cecilio Pardo
2024-10-29 17:13 ` Alan Mackenzie
2024-10-29 18:20   ` Cecilio Pardo
2024-10-29 19:31     ` Alan Mackenzie
2024-10-29 21:45       ` Cecilio Pardo
2024-10-30  6:02         ` Yuri Khan
2024-10-30 15:23           ` Eli Zaretskii
2024-10-30 16:51             ` Yuri Khan
2024-10-30 17:25               ` Eli Zaretskii
2024-10-30  3:27       ` Eli Zaretskii
2024-11-03 23:44 ` Cecilio Pardo
2024-11-04  0:21   ` Po Lu
2024-11-04  8:03     ` Cecilio Pardo
2024-11-04  9:35       ` Po Lu
2024-11-04 11:11         ` Cecilio Pardo
2024-11-04 11:49           ` Po Lu
2024-11-04 11:59             ` Cecilio Pardo
2024-11-04 13:29               ` Eli Zaretskii
2024-11-04 13:46                 ` Cecilio Pardo
2024-11-04 13:54                 ` Po Lu
2024-11-04 13:24             ` Eli Zaretskii
2024-11-04 14:09               ` Po Lu
2024-11-04 16:46                 ` Eli Zaretskii
2024-11-05  1:31                   ` Po Lu
2024-11-05  7:15                     ` Cecilio Pardo
2024-11-05  9:03                       ` Po Lu
2024-11-05  9:20                         ` Cecilio Pardo
2024-11-05 12:21                           ` Po Lu
2024-11-05 13:30                             ` Eli Zaretskii
2024-11-05 14:27                             ` Cecilio Pardo
2024-11-06  0:10                               ` Po Lu
2024-11-06 12:49                               ` Po Lu
2024-11-06 13:31                                 ` Eli Zaretskii
2024-11-07  0:25                                   ` Po Lu
2024-11-07  6:41                                     ` Eli Zaretskii
2024-11-07 14:36                                       ` Po Lu
2024-11-07 15:47                                         ` Eli Zaretskii
2024-11-07 16:58                                           ` Cecilio Pardo
2024-11-08  0:36                                           ` Po Lu
2024-11-05 13:13                     ` Eli Zaretskii
2024-11-04 13:18         ` Eli Zaretskii
2024-11-04 14:37           ` Po Lu
2024-11-04 16:49             ` Eli Zaretskii [this message]
2024-11-05  1:03               ` Po Lu
2024-11-05  7:09                 ` Cecilio Pardo
2024-11-05 13:06                 ` Eli Zaretskii
2024-11-04 12:27     ` Eli Zaretskii
2024-11-04 13:09       ` Po Lu
2024-11-04 13:33         ` Eli Zaretskii

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=865xp3ueoq.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=cpardo@imayhem.com \
    --cc=emacs-devel@gnu.org \
    --cc=luangruo@yahoo.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).