[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#49689: [FEATURE REQUEST] Explicitly report change of input method
From: |
Eli Zaretskii |
Subject: |
bug#49689: [FEATURE REQUEST] Explicitly report change of input method |
Date: |
Thu, 22 Jul 2021 09:11:08 +0300 |
> Date: Wed, 21 Jul 2021 18:40:54 -0400
> From: Boruch Baum <boruch_baum@gmx.com>
>
> Presently, a buffer's current input method is:
>
> 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
> 2] Aforementioned cryptic symbol is not guaranteed to be unique
> (BUG?).
There are too few short meaningful strings to guarantee uniqueness.
So, not a bug, but a mild misfeature due to screen estate constraints.
> 2.1] Example: Hebrew and Hebrew-new
>
> Please consider explicitly reporting changes to the input method. I've
> done this to my personal satisfaction locally by adding a single line to
> the end of each of functions `activate-input-method' and
> `deactivate-input-method', both in file `mule-cmds'.
>
> (message "Current input method is now: %s" current-input-method))
I don't think I understand the feature request. The message you
suggest is ephemeral: it will be removed on the next keystroke. So
it's not like it will be shown there for prolonged periods of time.
How will it help?
> This change has additional benefits:
>
> 1] Letting me know what I've done when I mis-type `C-\'.
Doesn't "C-h l" help you know that?
>
> 2] Letting me know what to select when performing `C-h I'
Please elaborate how does that message help with this last task.
Thanks.