Mercurial > vim
view runtime/keymap/korean.vim @ 30146:d58afefecd6c v9.0.0409
patch 9.0.0409: #{g:x} was seen as a curly-braces expression
Commit: https://github.com/vim/vim/commit/7c7e1e9b98d4e5dbe7358c795a635c6f1f36f418
Author: ii14 <ii14@users.noreply.github.com>
Date: Wed Sep 7 19:40:17 2022 +0100
patch 9.0.0409: #{g:x} was seen as a curly-braces expression
Problem: #{g:x} was seen as a curly-braces expression.
Solution: Do never see #{} as a curly-braces expression. (closes https://github.com/vim/vim/issues/11075)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Wed, 07 Sep 2022 20:45:03 +0200 |
| parents | 11b656e74444 |
| children |
line wrap: on
line source
" Maintainer: Jang Whemoon <palindrom615@gmail.com> " Last Change: Nov 24, 2020 " " " " Unlike Japanese or Chinese, modern Korean texts do not depends on conversion " to Hanja (Chinese character). Thus, general Korean text totally can be " covered without help of IME but this keymap. " " BUT, simply mapping each letter of Hangul with sequence of alphabet 1 by 1 " can fail to combine Hangul jamo (conconants and vowels) right. " For example, sequentially pressing `ㅅㅓㅇㅜㄹㄷㅐㅎㅏㄱㅛ` can not only be " combined as `서울대학교`, but also `성ㅜㄹ댛ㅏㄱ교`, which is totally " nonsense. " Though combining Hangul is deterministic with law that each letter must be " one of (consonant + vowel) or (consonant + vowel + consonant), there is no " way to apply such law without implementing input engine. " " Thus, user of this keymap should wait until previous hangul letter is " completed before typing next one. To reduce such inconvenience, I suggest to " set `timeoutlen` with their own value. (default value is 1000ms) source <sfile>:p:h/korean-dubeolsik_utf-8.vim