diff options
| author | altermo <107814000+altermo@users.noreply.github.com> | 2026-07-18 18:20:41 +0200 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2026-07-18 12:20:41 -0400 |
| commit | a2dfa195b2b9db3f6c442a131e1c9268989fa70d (patch) | |
| tree | 34afb3fd6a2c389c160ae8c6b828b21fb8719a29 /test/functional/vimscript/executable_spec.lua | |
| parent | 952e59347e053a61cb621e56625c846b249236a0 (diff) | |
| download | rneovim-a2dfa195b2b9db3f6c442a131e1c9268989fa70d.tar.gz rneovim-a2dfa195b2b9db3f6c442a131e1c9268989fa70d.tar.bz2 rneovim-a2dfa195b2b9db3f6c442a131e1c9268989fa70d.zip | |
feat(lua): vim.keycode() gets structured parse result #38636
Problems:
1. Can't get individual parts of a key-chord separately: modifiers, key.
2. Can't separate a key-combo into individual key-chords.
Solution:
Enhance `vim.keycode()` to optionally return a structured parse result
as a list of key-chords:
- `key_raw` the key-chord (problem 2)
- `mod` the modifiers of `key_raw` (problem 1)
- `key_orig` the key part of the key-chord, only here if differing from `key`
(this doesn't solve any of the above mentioned problems, but it may provide
useful and it's (in terms of code) free)
- `key` a normalized version of `key_orig` (solving problem 1), example(the
first is `key_orig` and second is `key`): `lt` and `<`, `Bar` and `|` (in
`<C-Bar>`)
Diffstat (limited to 'test/functional/vimscript/executable_spec.lua')
0 files changed, 0 insertions, 0 deletions