Bug#990316: Add GLFW_IM_MODULE=fcitx on ibus and fcitx5 to enable IME in kitty
Hi,
\
On Thu, 2021-11-18 at 16:09 +0100, Gunnar Hjalmarsson wrote:
> On 2021-11-18 15:29, Osamu Aoki wrote:
> > On Mon, 2021-11-15 at 15:11 +0100, Gunnar Hjalmarsson wrote:
> > > 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...
>
> https://github.com/kovidgoyal/kitty/issues/469#issuecomment-419406438
Hmmm...I see. This is worrying
Anyway, situation of enabling IM needs help from someone understanding GLFW related
backend keyboard input handling. The successful user seem to use "sway" for Desktop
management. Is there any other programs using similar backend.
If problem is happening with backend using xim, that is likely the situation just
like GTK. But this seems to indicate otherwise.
Anyway, those who seems having trouble setting up ibus or fcitx5 didn't set up
environment variable properly. There are too much noise. So we need feedback from
good tester reporting situation with versions involved (ibus, fcitx5, ...)
Current in testing are:
kitty 0.19.3-1
ibus 1.5.25-3
fcitx5 5.0.9-2
sway 1.5.1-2
(fcitx 1:4.2.9.8-3)
> > I am not sure what is "the other way around"?
>
> The purpose of im-config is to make sure that an IM framework — if
> present — is launched and configured by default.
>
> > So for wayland ready IM (ibus and fcitx5?) it may be right to set
> > such setting.
>
> Please remember that im-config doesn't do anything in case of IBus on a
> GNOME desktop, but we defer to GNOME's mechanisms for launching and
> configuring IBus.
Yes. I plan to keep it this way for GNOME.
Wei, Please let us know XDG_CURRENT_DESKTOP on the system you tested. What do you
get on sway system who try to use kitty?
> > Tell us how this all fit together.
>
> +1
>
Reply to: