From: Visuwesh <visuweshm@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eli Zaretskii <eliz@gnu.org>,
Andreas Schwab <schwab@linux-m68k.org>,
Boruch Baum <boruch_baum@gmx.com>,
49689@debbugs.gnu.org
Subject: bug#49689: [FEATURE REQUEST] Explicitly report change of input method
Date: Mon, 22 Aug 2022 12:45:17 +0530 [thread overview]
Message-ID: <87v8qkagvu.fsf@gmail.com> (raw)
In-Reply-To: <87v8qla2q6.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sun, 21 Aug 2022 20:08:49 +0200")
[ஞாயிறு ஆகஸ்ட் 21, 2022] Lars Ingebrigtsen wrote:
>
> Andreas Schwab <schwab@linux-m68k.org> writes:
>
>>>> 1] Only reported in the form of a cryptic symbol on the mode line.
>>>
>>> You get the full description if you hover the mouse pointer above that
>>> symbol (it's actually a short string). You can also do this:
>>>
>>> M-: current-input-method RET
>>
>> Or even C-h I.
>
> I think the conclusion here was that we don't want to change how this
> works, so I'm closing this bug report.
FWIW, sometimes I wish Emacs was a little more explicit about changing
input methods, even more so now that transient input methods are a
thing. Sometimes, I find myself in an odd state of using an input
method when I activate "compose" transiently (I have it bound to M-m):
this could just be my buggy command though. The message "Loading ..."
helps but not when you switch the second time. The mode-line indicator
is not a great solution when the indicator is a single letter (I use a
proportional font for the mode-line).
next prev parent reply other threads:[~2022-08-22 7:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 22:40 bug#49689: [FEATURE REQUEST] Explicitly report change of input method Boruch Baum
2021-07-22 6:11 ` Eli Zaretskii
2021-07-22 6:52 ` Boruch Baum
2021-07-22 7:56 ` Andreas Schwab
2022-08-21 18:08 ` Lars Ingebrigtsen
2022-08-22 7:15 ` Visuwesh [this message]
2022-08-23 7:37 ` Juri Linkov
2022-08-23 13:38 ` Visuwesh
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=87v8qkagvu.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=49689@debbugs.gnu.org \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=schwab@linux-m68k.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).