Mercurial > vim
view runtime/keymap/README.txt @ 33297:6340c608ca54 v9.0.1914
patch 9.0.1914: Vim9: few issues when accessing object members
Commit: https://github.com/vim/vim/commit/1db151436541a3e64cdd5e3d9eb3ace1ce1e1ad0
Author: Yegappan Lakshmanan <yegappan@yahoo.com>
Date: Tue Sep 19 20:34:05 2023 +0200
patch 9.0.1914: Vim9: few issues when accessing object members
Problem: Vim9: few issues when accessing object members
Solution: When calling an object method, check for null object.
Accessing a Dict object member doesn't work.
closes: #13119
closes: #13123
closes: #13124
Signed-off-by: Christian Brabandt <cb@256bit.org>
Co-authored-by: Yegappan Lakshmanan <yegappan@yahoo.com>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Tue, 19 Sep 2023 20:45:06 +0200 |
parents | 3fc0f57ecb91 |
children |
line wrap: on
line source
keymap files for Vim One of these files is loaded when the 'keymap' option is set. The name of the file consists of these parts: {language}[-{layout}][_{encoding}].vim {language} Name of the language (e.g., "hebrew", "greek") {layout} Optional: name of the keyboard layout (e.g., "spanish", "russian3"). When omitted the layout of the standard US-english keyboard is assumed. {encoding} Optional: character encoding for which this keymap works. When omitted the "normal" encoding for the language is assumed. Use the value the 'encoding' option: lower case only, use '-' instead of '_'. Each file starts with a header, naming the maintainer and the date when it was last changed. If you find a problem in a keymap file, check if you have the most recent version. If necessary, report a problem to the maintainer. The format of the keymap lines below "loadkeymap" is explained in the Vim help files, see ":help keymap-file-format".