From: Jones Stephen <happyojones@gmail.com>
To: 74975@debbugs.gnu.org
Subject: bug#74975: Emacs app in MacOS, The keydown events for ESC are consumed by emacs and, IIUC, will not be sent to other app like Squirrel.
Date: Thu, 19 Dec 2024 20:06:46 +0800 [thread overview]
Message-ID: <CAOFab0m7Lt7a0DFB-e3zzFT1OKc6SMpDA+8374ZofEpPupFv9A@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 435 bytes --]
Hello:
I have encountered an issue with the Emacs app on macOS. Specifically, the
`ESC` keydown events are consumed by Emacs and, as far as I understand, are
not passed to other applications like Squirrel (a macOS input method). This
behavior seems problematic in certain scenarios.
For reference, a related issue has been discussed here: [
https://github.com/rime/squirrel/issues/625](https://github.com/rime/squirrel/issues/625)
.
[-- Attachment #2: Type: text/html, Size: 589 bytes --]
reply other threads:[~2024-12-19 12:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CAOFab0m7Lt7a0DFB-e3zzFT1OKc6SMpDA+8374ZofEpPupFv9A@mail.gmail.com \
--to=happyojones@gmail.com \
--cc=74975@debbugs.gnu.org \
/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).