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

Fix for fcitx does not work, but fix for xim immodule works for fcitx #50

Closed
nemo-nullius opened this issue Sep 20, 2017 · 3 comments
Closed

Comments

@nemo-nullius
Copy link

At first, thank you so much for this wonderful fix.

It is very strange that in my case, after patching this fix, I cannot get it to work. Everytime when I switch to fcitx in sublime text, it will keep switching back to English keyboard again, and I cannot type in any Chinese characters at all. However, after I delete all the lines from 38 to 115 in sublime-imfix.c (all the codes concerning fcitx are deleted and xim are left) and then re-compile and use it, this time it works very well. I can type in Chinese characters with fcitx as usual! So I am very confused about the outcome - why codes for fcitx does not work for fcitx but those for xim does work for fcitx in my case?

My environment is as follows:

  • OS: ubuntu 14.04 + i3wm/xfce4
  • Imput Method: fcitx 4.2.8.5
  • Sublime Ver 3.0, Build 3143
  • sublime-text-imfix: commit de1cc97 (latest)

Thank you for your help!

@lyfeyaj
Copy link
Owner

lyfeyaj commented Sep 21, 2017

Couldn't reproduce ...

@nemo-nullius
Copy link
Author

nemo-nullius commented Sep 22, 2017

It is indeed quite strange... But thank you so much all the same for your help!

By the way, I also find that the behavior of deleting is not correct in sublime with fcitx after patching. Everytime when I press backspace, it deletes the words in sublime rather than those in the input box of fcitx. This issue seems to be prevalent and seems to have perplexed many people on the internet. Do you know any solution to this problem please?

@nemo-nullius
Copy link
Author

nemo-nullius commented Sep 22, 2017

I have come up with a method to work around this backspace problem. See #46

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