-
Notifications
You must be signed in to change notification settings - Fork 15
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
compare to functionality provided by built-in keymap #2
Comments
Thanks for the suggestion. I've linked this thread in the README. Please let me know if there are any errors. My understandingThe
would make “B” come out as “Б”. These mappings can be toggled with
but do not apply:
Vim includes 70-odd keymap files by default (in My takeIt's wonderfully thoughtful to include this functionality natively, but for anyone who actually uses a dedicated system IME for anything other than vim, it's hard to imagine wanting mbyte-keymaps on top. Now you have two layers of IM management to think about: there might be subtle differences in layout, behavior, or visual feedback; there will most certainly be two different keyboard shortcuts for toggling IMs; and vim offers no visual indication for which keymap is active. For non-alphabetic languages like Chinese, keymaps would be virtually impossible to implement. |
I have been trying to get Korean / English working more smoothly, and from my experience I can address two reasons why
With the system IME, as you type the six letters of the word, they are progressively displayed as follows:
Without this functionality, my simplistic
|
This plug-in seems to solve a problem similar to
:help mbyte-keymap
. How about explaining the differences inREADME.md
?The text was updated successfully, but these errors were encountered: