-
Notifications
You must be signed in to change notification settings - Fork 111
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
Sometimes some characters bypass fcitx5 #419
Comments
I only know sometimes this happens on xim + chromium. but with that being said, the issue is not on the fcitx side but on the emacs side. I don't know if you have anything special on the emacs that triggers this because I don't know other people report the same problem. To help workaround your issue, actually I suggest to switch to emacs's pgtk branch. I heard that it's recently merged into emacs mainstream. It makes emacs use gtk for rendering and input method, which essentially use the gtk im module for input method. Since you're using arch, try this AUR package: https://aur.archlinux.org/packages/emacs-pgtk-native-comp-git/ . Let me know if you have the same problem with pgtk enabled emacs. |
OK, I'll try emacs-pgtk. |
Very glad that emacs-pgtk works well. |
Describe the bug
I am using fcitx5 to input Chinese in emacs.
When I input Chinese, I expect that fcitx5 captures all characters that I type and converts them into Chinese characters.
But sometimes one or more English characters bypass fcitx5 and go to the screen directly.
For example, I want to input "文件". So I enable fcitx5 and type "wenjian".
Sometimes, only "wejian" is captured by fcitx5, the missing "n" goes directly into the application such as emacs.
Such a problem does not occur every time. But it occurs unpredictably, which is quite annoying.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The typed characters are all captured by fcitx5.
Desktop (please complete the following information):
The output of "fcitx5-diagnose" is:
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: