[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#49689: [FEATURE REQUEST] Explicitly report change of input method
From: |
Boruch Baum |
Subject: |
bug#49689: [FEATURE REQUEST] Explicitly report change of input method |
Date: |
Wed, 21 Jul 2021 18:40:54 -0400 |
User-agent: |
NeoMutt/20180716 |
Presently, a buffer's current input method is:
1] Only reported in the form of a cryptic symbol on the mode line.
2] Aforementioned cryptic symbol is not guaranteed to be unique
(BUG?).
(length input-method-alist)
=> 205
(length (delete-duplicates
(mapcar (lambda (x) (nth 3 x)) input-method-alist)))
=> 183
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))
This change has additional benefits:
1] Letting me know what I've done when I mis-type `C-\'.
2] Letting me know what to select when performing `C-h I'
--
hkp://keys.gnupg.net
CA45 09B5 5351 7C11 A9D1 7286 0036 9E45 1595 8BC0
- bug#49689: [FEATURE REQUEST] Explicitly report change of input method,
Boruch Baum <=