unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@linkov.net>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44266@debbugs.gnu.org
Subject: bug#44266: Transient input methods
Date: Sun, 01 Nov 2020 20:24:10 +0200	[thread overview]
Message-ID: <87blgh6jj9.fsf@mail.linkov.net> (raw)
In-Reply-To: <87r1pd9m9f.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 01 Nov 2020 15:37:00 +0100")

>> The following patch addresses such issues of the current input method
>> implementation by providing a new feature of transient input methods.
>
>> A transient input method is enabled temporarily for entering a key sequence,
>> and is disabled automatically afterwards.
>
> I like the idea, I think.  But just thinking out loud without having
> read the code closely -- would it perhaps be even more useful to have
> the transient method in place until you `C-x \' again?
>
> Then you could
>
> `C-x \ ...  type a couple of words in that method C-x \'

This is achievable already by shorter key sequence:
`C-\ ...  type a couple of words in that method C-\'

> I'm not at all sure, but I think that perhaps people would more often
> type in a couple of words than just a single key sequence?

This feature is intended as an equivalent of the X Compose Multi_key
that inserts a single character, whereas X layouts switcher that activates
a layout to insert a couple of words corresponds to Emacs non-transient
input methods switched by C-\.





  reply	other threads:[~2020-11-01 18:24 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-27 20:43 bug#44266: Transient input methods Juri Linkov
2020-10-28 11:40 ` Lars Ingebrigtsen
2020-10-29  4:48 ` Richard Stallman
2020-11-01 21:36   ` Juri Linkov
2020-11-05 20:14     ` Juri Linkov
2020-11-06  8:33       ` Juri Linkov
2020-11-01 14:37 ` Lars Ingebrigtsen
2020-11-01 18:24   ` Juri Linkov [this message]
2020-11-02  5:41   ` Richard Stallman

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=87blgh6jj9.fsf@mail.linkov.net \
    --to=juri@linkov.net \
    --cc=44266@debbugs.gnu.org \
    --cc=larsi@gnus.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).