-
Notifications
You must be signed in to change notification settings - Fork 496
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to trigger fcitx5 when using neovide #1006
Comments
Same problem |
Same problem😭 |
same here with 0.9.0 |
same |
Anyone that found a solution to this problem? |
same here |
same 0.10.3 |
Same here with 0.10.3 |
I guess it needs to update winit |
I builded it from source code,and the problem isn't fixed
|
neovide/glutin still depends on neovide/winit |
Same problem. |
Can't input Chinese in MacOS using squirrel as well. |
Same with 0.10.3 still |
This should be fixed by #1899, it would be great if you can test that. |
Any config required? |
Yes https://fcitx-im.org/wiki/FAQ#Non_Gtk.2FQt_Wayland_Application_.28Alacritty.2C_kitty.2C_etc.29 and https://www.csslayer.info/wordpress/linux/use-plasma-5-24-to-type-in-alacritty-or-any-other-text-input-v3-client-with-fcitx-5-on-wayland/. A reboot or at least a logout might also be needed. |
Also note that I'm still working on the pre-edit support. And the positioning of the popup also has some issues and waiting for rust-windowing/winit#2886. Another thing that will be added later is the possibility to dynamically enable and disable the IME support, so that it can be enabled in only insert mode for example. |
It looks like it's not fixed on X11 yet. But Wayland should work, at least if you follow the above instructions. |
@fredizzimo you might need to go to fcitx5's config of xim frontend and check "on the spot" and then restart fcitx5 if you want to try preedit on xim. There's some historical reason that xim's preedit is not enabled by default. https://bugs.freedesktop.org/show_bug.cgi?id=1580 |
@wengxt, the problem with X11 is that nothing seems to be triggered at all for me at the moment, and other have reported the same in #1899. On Wayland I can get it working by adding the virtual keyboard as described above. On X11 there appears to be some communication with the server, since the position is changed, and it shows a popup when toggling languages. But until I started working on this a few days ago, I did barely know what IME was, so it could be a configuration issue on my side. Anyway, if fcitx5 triggers on some system, that would be very valuable information to add to the corresponding winit issue rust-windowing/winit#2888. BTW, if someone wants to check out the IME "on the spot" pre-edit branch I'm working on, it's here https://github.com/fredizzimo/neovide/tree/fsundvik/ime. It still does not show selected texts, and the rendering is quite hacky and does not support transparency. I think I wait for #1870 until I fix that. The fcitx popup will also overlap the text in some cases until this rust-windowing/winit#2889 is integrated. I also don't know what to do when you type long lines, and the text would need to be scrolled. |
X11 should now work with #1899 |
Describe the bug
The fcitx5 App is an input method engine that I use for input Chinese. It works on most of my desktop applications like Neovim-QT, Telegram, and Firefox...etc. I recently switched to use neovide. It meets my needs very well, except for one thing: I can't use the hotkey to trigger the input method.
I am using
<CTRL>+<SHIFT>
and<CTRL>+<SPACE>
to trigger my fcitx5. When I press<CTRL>+<SPACE>
, it triggers the inner completion menu, and when I press<CTRL>+<SHIFT>
, nothing happens.It's weird because whatever the hotkey I used, the nvim-qt can work as expected, so maybe it is not my neovim configuration error. Moreover, no error report from
fcitx5-diagnose
, so maybe it is not my fcitx5 configuration error.But I can't find any issues related to fcitx5, so I am here to ask for help.
To Reproduce
Steps to reproduce the behavior:
fcitx-configtool
and add rime below theKeyboard-English
Expected behavior
The behavior I expect is like nvim-qt. I've recorded a video to show the difference.
2021-10-10.20-54-20.mp4
Desktop (please complete the following information):
Please run
neovide --log
and paste the contents of the.log
file here:Log:
Additional context
My rime settings: https://github.com/Avimitin/rime
My NeoVIM settings: https://github.com/Avimitin/nvim
fcitx5 diagnose output: https://pastebin.com/QQ0tERtZ
The text was updated successfully, but these errors were encountered: