From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Disable text conversion in map-ynp
Date: Mon, 06 May 2024 22:14:28 +0800 [thread overview]
Message-ID: <87h6fb3u4b.fsf@yahoo.com> (raw)
In-Reply-To: <86o79jawhp.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 06 May 2024 16:41:22 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Thanks, but I don't think I understand the issue, given the above
> description. For starters, you changed read-event to read-key, not
> the other way around. So does it mean it's read-key that is supposed
> to prevent text conversion, while read-event does not?
Yes, sorry. See the doc string of read-key:
Also in contrast to `read-event', input method text conversion
will be disabled while the key sequence is read, so that
character input events will always be generated for keyboard
input.
> Also, read-event disables input methods if its 2nd argument is nil
> (which it is in this case) -- does this mean that fact does not affect
> the Android input methods?
INHERIT-INPUT-METHOD only affects Emacs input methods, yes.
> 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. I'm not sure
the former is any more correct than calling read-key.
> 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.
next prev parent reply other threads:[~2024-05-06 14:14 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 [this message]
2024-05-06 14:56 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87h6fb3u4b.fsf@yahoo.com \
--to=luangruo@yahoo.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.