Closed denis-savran closed 4 years ago
I examined fcitx.py in fcitx.vim repository and found out the following:
1) The plugin calls deactivate (switchToEnglish
) method only when the fcitx state == 2
(2 for active) and then enables inputtoggle
flag.
2) The plugin calls activate (restore
) method only when inputtoggle
flag is enabled.
Calling fcitx-remote
without any arguments returns current fcitx state
.
The problem of "Changing vi mode to insert mode by pressing o or O does not restore the input method." is fixed in version 1.4.1 .
The other problem will be fixed in version 1.4.2 .
Thanks for your feedback !
Tried it on PyCharm 2019.3.1 with a following line added to JVM options (fixes a problem of input method switching via fcitx):
-Dauto.disable.input.methods=false
Everything works perfectly. Thank you for the fix.
Found two problems regarding input method restoration.
IdeaVim 0.54 IdeaVimExtension 1.4.0 fcitx 4.2.9.6
Changing vi mode to insert mode by pressing
i
always changes the input method toru
.Steps to reproduce:
:set keep-english-in-normal-and-restore-in-insert
to~/.ideavimrc
i
. The input method is automatically changed toru
.us
.i
. Input method is automatically changed toru
.Expected behaviour: After changing to the insert mode by pressing
i
the input method is automatically changed tous
.Changing vi mode to insert mode by pressing
o
orO
does not restore the input method.Steps to reproduce:
:set keep-english-in-normal-and-restore-in-insert
to~/.ideavimrc
i
. The input method is automatically changed toru
.o
. The input method is not changed and is equal tous
.Expected behavior: After changing to the insert mode by pressing
o
the input method is automatically changed toru
.Plugin fcitx.vim also uses fcitx to change the input method and has the behavior described in the 'Expected behavior' sections.