Skip to content
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

Doesn't seem to work when there are more than 2 input methods (e.g. German) #39

Open
x-ji opened this issue May 6, 2019 · 3 comments
Open

Comments

@x-ji
Copy link

x-ji commented May 6, 2019

It works if I input Chinese in Emacs using Sogou Input. However, if I input German (using the built-in German keyboard layout) in Emacs, it doesn't work.

When I press Esc, the input method is indeed switched back to US English. However, When I press i again, the input method is not switched back to German, but seemingly to Sogou. However, it doesn't actually enter Chinese, but rather directly enters English characters.

Under Linux fcitx, the mechanism always works in Emacs, no matter what language I'm inputting using fcitx.

A quick look at the source code seems to suggest that the program is hard-coded to switch back to the Chinese input:

void active(){
    switch_to(CHINESE_KEYBOARD_LAYOUT);
}

Would it be possible to let it switch to the last active keyboard layout? Or maybe to let it just simulate the pressing of a key combination, e.g. Ctrl + Space, whenever Esc is pressed within Emacs.

@jiegec
Copy link
Collaborator

jiegec commented May 7, 2019

fcitx-remote is stateless. It does not know the original state.

@x-ji
Copy link
Author

x-ji commented May 11, 2019

I see. But as I mentioned, would it be possible to just let fcitx-remote simulate a shortcut such as Ctrl-SPC, which would always switch to the previously selected input method?

@jiegec
Copy link
Collaborator

jiegec commented Dec 23, 2019

You can use GENERAL method described in README.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants