Map IME composition input to Latin characters in non-insert mode. #9859
+82
−10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it:
CJK languages have a character count that far exceeds the number of keys on a keyboard, requiring multiple keystrokes to compose a single character. This makes it impossible to use a simple langmap to control Vim's operations. Traditionally, the autoSwitchInputMethod approach is used to automatically switch input methods, but this method has some drawbacks:
I added an option
vim.mapIMEComposition.enable(and the correspondingvim.mapIMEComposition.map) to enable mapping IME composition input to Latin characters.This allows users to control VIM's operations without switching CJK input methods.
For me, a consistent input method across various modes has greatly enhanced my experience of using vscodevim and Chinese input.
Implementation Details
To achieve this functionality, each character of the composition needs to be processed as a separate input, which requires the ability to interrupt the IME's composition state.
VSCode does not provide such functionality, so I used some clever implementation methods to interrupt the IME's composition state by switching the current focus target.
example:
This is not an ideal solution, but it works fine most of the time, with some issues only in extreme cases (when I purposely tap the keyboard quickly in succession).
Additional modifications
I removed some unnecessary async prefixes from functions, slightly reducing the occurrence rate of input issues.
Configuration Example
Relative Issues
#9858