From: Po Lu <luangruo@yahoo.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Android input methods
Date: Wed, 15 Feb 2023 10:13:44 +0800 [thread overview]
Message-ID: <87pmabu147.fsf@yahoo.com> (raw)
In-Reply-To: <83k00kchap.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 14 Feb 2023 19:01:34 +0200")
Eli Zaretskii <eliz@gnu.org> writes:
> They should. But note that those modes could enter recursive-edit in
> the minibuffer or elsewhere, and let users edit parts of the display,
> in which case we do want the IME back on.
OK, I will keep that in mind.
>> > Don't know yet. I suggest to have some variable that Lisp can bind to
>> > control this. Then we'll find the cases where it is needed as we go.
>>
>> OK, I will implement input method support along the lines of what was
>> discussed here.
>
> Thanks. I understand that, if single-key input is expected, we are
> talking about some intermediate hidden buffer, used to compare what
> the IME produces with what was there before, and emit synthetic
> keystrokes, is that right?
Right, if that is all the input method supports. But Emacs will try
hard to ask the input method to send plain key events first.
next prev parent reply other threads:[~2023-02-15 2:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-12 12:58 textconv.c Eli Zaretskii
2023-02-12 14:05 ` textconv.c Po Lu
2023-02-12 14:32 ` textconv.c Eli Zaretskii
2023-02-12 15:06 ` textconv.c Eli Zaretskii
2023-02-12 15:35 ` textconv.c Po Lu
2023-02-12 15:27 ` Android input methods (was: Re: textconv.c) Po Lu
2023-02-12 15:57 ` Eli Zaretskii
2023-02-13 2:21 ` Android input methods Po Lu
2023-02-13 13:49 ` Eli Zaretskii
2023-02-13 14:37 ` Po Lu
2023-02-13 15:17 ` Eli Zaretskii
2023-02-13 17:04 ` Eli Zaretskii
2023-02-14 1:57 ` Po Lu
2023-02-14 14:32 ` Eli Zaretskii
2023-02-14 15:14 ` Po Lu
2023-02-14 17:01 ` Eli Zaretskii
2023-02-15 2:13 ` Po Lu [this message]
2023-02-12 16:00 ` Android input methods (was: Re: textconv.c) Lynn Winebarger
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=87pmabu147.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 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).