On 2021-11-21 03:42, Osamu Aoki wrote:
Considering kitty is the only user of GLFW_IM_MODULE variable on Debian and it
shouldn't be turned on by default according to the upstream, I propose to add
following content as README.Debian in the Debian package of kitty.
----------
# Input Method support
You can enable input of non-Latin characters to the kitty terminal as follows:
1. Install required a set of input method program based on ibus or fcitx5
2. Place the following file named "kitty" in PATH
(e.g., ~/.local/bin or /usr/local/bin)
3. Meke "kitty" script an executable. (`chmod 755 kitty`)
---
#!/bin/sh -e
GLFW_IM_MODULE=ibus exec /usr/bin/kitty "$@"
---
fcitx5 uses the same communication protocol as ibus. So you use "ibus" even for
"fcitx5". Other input method infrastructure such as "fcitx" and "uim" are not
supported.
----------
Yeah, such a wrapper is a convenient way to specify an environment
variable for a specific application.
For im-config, I think it is about time to kill upstream non-supported known
broken
xim support by dropping to start daemon from im-config which sets how Debian
behaves
as installed. xterm and rxvt may loose CJK input but we will get less bug
report on
ill-configured modern GTK/Qt apps using xim.
I'm not sure I understand what you mean by that. Any chance you can
elaborate somewhere else? (This is no longer an im-config bug.)
--
Rgds,
Gunnar
