From: Eli Zaretskii <eliz@gnu.org>
To: Po Lu <luangruo@yahoo.com>
Cc: emacs-devel@gnu.org
Subject: Re: Disable text conversion in map-ynp
Date: Mon, 06 May 2024 17:56:02 +0300 [thread overview]
Message-ID: <86le4nat19.fsf@gnu.org> (raw)
In-Reply-To: <87h6fb3u4b.fsf@yahoo.com> (message from Po Lu on Mon, 06 May 2024 22:14:28 +0800)
> From: Po Lu <luangruo@yahoo.com>
> Cc: emacs-devel@gnu.org
> Date: Mon, 06 May 2024 22:14:28 +0800
>
> > and if so, is there a way to suppress input methods on Android while
> > still calling read-event?
>
> There could be, but it would entail calling read-char rather than
> read-event, or introducing a new parameter to read-event.
Don't we have some variable that could be bound around the call to
read-event to suppress text-conversion? If not, we should, because
this is definitely not the last situation where it could get in the
way.
> > IOW, I'd like to keep using read-event, but make sure text-conversion
> > doesn't happen, instead of switching to read-key. And if that's
> > impossible for some reason, how about using read-key only on Android?
>
> I think an informed conclusion would be easier to draw if you directed
> me to previous occasions where issues arose from switching from read-key
> to read-event in similar contexts.
I don't have it ready. But I'm not sure how would that help. If you
look at what read-key does and compare that to read-event, you will
see that the differences are so significant as to thwart any attempt
to figure out when and how these two will behave differently.
But okay, see these:
bug#24635
bug#29150
https://lists.gnu.org/archive/html/emacs-devel/2020-11/msg00601.html
next prev parent reply other threads:[~2024-05-06 14:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-06 12:06 Disable text conversion in map-ynp Eli Zaretskii
2024-05-06 12:46 ` Po Lu
2024-05-06 13:41 ` Eli Zaretskii
2024-05-06 14:14 ` Po Lu
2024-05-06 14:56 ` Eli Zaretskii [this message]
2024-05-07 0:48 ` Po Lu
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=86le4nat19.fsf@gnu.org \
--to=eliz@gnu.org \
--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).