From: Robert Pluim <rpluim@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: andremegafone@gmail.com, tor.a.s.kringeland@ntnu.no,
52245@debbugs.gnu.org
Subject: bug#52245: Wishlist: cycle input methods
Date: Wed, 08 Dec 2021 15:51:18 +0100 [thread overview]
Message-ID: <87sfv3p2u1.fsf@gmail.com> (raw)
In-Reply-To: <83h7bjw4ox.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 08 Dec 2021 16:29:18 +0200")
>>>>> On Wed, 08 Dec 2021 16:29:18 +0200, Eli Zaretskii <eliz@gnu.org> said:
>> From: Robert Pluim <rpluim@gmail.com>
Eli> Sounds good, but I don't understand how you will pull out the trick in
Eli> the last sentence. How will Emacs know to "just deactivate" instead
Eli> of cycling?
>>
>> Similar to how it knows to toggle today, by storing an "I was
>> activated via prefix" state in a defvar-local state variable.
Eli> Hmm... so just C-\ to activate is not enough to cause the toggle back?
No, because you need to distinguish "Iʼm cycling through
default-input-method" from "previous invocation used prefix", since in
the former you need to look up the current input method in
default-input-method and then activate the next one.
Hmm, what do we expect for the following sequence, assuming
default-input-method of '(a b c), and no input method activated.
1. C-\ ; activates a
2. C-u C-\ d RET ; activates d
3. C-\ ; back to a, I guess
4. C-\ ; activates b
Or do we want step 3 to be 'deactivate input method'?
>> What did you think of the C-u C-u C-\ suggestion to mean "always
>> deactivate"? Or do you feel itʼs unnecessary?
Eli> Given the above, some way of turning off the input method is
Eli> necessary, I think.
Escape hatches are always good, especially if we end up with confusing
behaviour :-)
Robert
--
next prev parent reply other threads:[~2021-12-08 14:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-02 15:30 bug#52245: Wishlist: cycle input methods Tor Kringeland
2021-12-02 15:49 ` Robert Pluim
2021-12-02 18:14 ` Eli Zaretskii
2021-12-03 8:42 ` Robert Pluim
2021-12-07 15:57 ` André A. Gomes
2021-12-07 16:30 ` Robert Pluim
2021-12-07 17:11 ` Eli Zaretskii
2021-12-08 9:40 ` Robert Pluim
2021-12-08 13:26 ` Eli Zaretskii
2021-12-08 13:44 ` Robert Pluim
2021-12-08 14:29 ` Eli Zaretskii
2021-12-08 14:51 ` Robert Pluim [this message]
2021-12-11 14:31 ` John Ankarström
2021-12-11 20:07 ` André A. Gomes
2021-12-23 18:02 ` Juri Linkov
2021-12-23 18:27 ` Eli Zaretskii
2021-12-23 18:45 ` Juri Linkov
2021-12-07 15:51 ` André A. Gomes
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=87sfv3p2u1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=52245@debbugs.gnu.org \
--cc=andremegafone@gmail.com \
--cc=eliz@gnu.org \
--cc=tor.a.s.kringeland@ntnu.no \
/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).