[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Android input methods
From: |
Po Lu |
Subject: |
Re: Android input methods |
Date: |
Wed, 15 Feb 2023 10:13:44 +0800 |
User-agent: |
Gnus/5.13 (Gnus v5.13) |
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.
- Re: Android input methods (was: Re: textconv.c), (continued)
- Re: Android input methods (was: Re: textconv.c), Eli Zaretskii, 2023/02/12
- Re: Android input methods, Po Lu, 2023/02/12
- Re: Android input methods, Eli Zaretskii, 2023/02/13
- Re: Android input methods, Po Lu, 2023/02/13
- Re: Android input methods, Eli Zaretskii, 2023/02/13
- Re: Android input methods, Eli Zaretskii, 2023/02/13
- Re: Android input methods, Po Lu, 2023/02/13
- Re: Android input methods, Eli Zaretskii, 2023/02/14
- Re: Android input methods, Po Lu, 2023/02/14
- Re: Android input methods, Eli Zaretskii, 2023/02/14
- Re: Android input methods,
Po Lu <=
- Re: Android input methods (was: Re: textconv.c), Lynn Winebarger, 2023/02/12