Bug#988540: im-config: breaks the keyboard configuration
On 2022-05-23 11:49:21 +0900, Osamu Aoki wrote:
> Users may no longer be able to use xterm **reliably for some
> non-ASCII inputs** when ibus is **activated**.
I'm wondering what you mean by that. I recall that:
1. If im-config is run after my XKB settings, then my keyboard
configuration is broken (probably overridden by im-config's
own settings). This means that ibus is activated, right?
2. If after that, I apply my XKB settings again, then things work
as usual (even for xterm), possibly except for applications
that are currently running (in particular xterm, but this is
not related to ibus, as this is an issue I reported in 2012:
bug 661295). So, if ibus is activated (see (1)), this would
mean that it shouldn't affect xterm, even for most non-ASCII
inputs (I recall that I use accented letters, possibly via
dead keys, and math symbols: xterm is receiving the Unicode
character correctly, so I wonder why it would depend on the
code point).
Or did you mean that if I want to remap the keyboard with ibus
instead of XKB, then it would not work with xterm[*]?
[*] in case of testing, bug 661295 needs to be taken into account,
i.e. one should test by starting xterm after any config change.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: