Bug#990316: Add GLFW_IM_MODULE=fcitx on ibus and fcitx5 to enable IME in kitty
Hi,
On Mon, 2021-11-15 at 15:11 +0100, Gunnar Hjalmarsson wrote:
> Control: tag -1 patch
>
> Thanks for your patch, Chen Shijie. As Osamu said, adding that variable
> would be trivial and without a risk to affect other applications.
>
> Reading <https://github.com/kovidgoyal/kitty/issues/469> makes me still
> hesitate, though. If I understand it correctly, the principal kitty
> developer has intentionally not enabled IME input by default due to
> claimed efficiency issues and bugs.
I am not sure which comment are you talking...
> im-config works the other way around. As soon as some input method
> framework such as IBus or fcitx5 is installed, im-config sets the
> related variables and launches the daemon. And it does so by default.
Kitty seems to use library which can get key input from different source path. This
is just like GTK and Qt apps are. I am not sure what is "the other way around"?
> In the light of that, I'm wondering if letting im-config set
> GLFW_IM_MODULE is the right thing to do.
>
Anyway, we need to get feed back from Wei.
As I don't use kitty, I am not the best person to judge what should be the best
default. At least I now understand kitty seems to be a terminal program running on
wayland environment without using GTK nor Qt.
It looks to me kitty is neither GTK nor Qt, without explicit environment variable
setting to use ibus, it use dbus? or xim? . This is just like GTK and Qt apps
behave. So for wayland ready IM (ibus and fcitx5?) it may be right to set such
setting.
Tell us how this all fit together.
Regards,
Osamu
Reply to: