diff options
| author | Marc André Tanner <mat@brain-dump.org> | 2016-08-20 16:01:43 +0200 |
|---|---|---|
| committer | Marc André Tanner <mat@brain-dump.org> | 2016-08-24 11:10:00 +0200 |
| commit | c0e86f811b3a8e4f45768db86e97d1b0fda5616f (patch) | |
| tree | 0dfc6da2764d6999256338e86180765b53abc633 /README.md | |
| parent | c7df560b818224d9a9ca3b0ba31a54312dc7062b (diff) | |
| download | vis-c0e86f811b3a8e4f45768db86e97d1b0fda5616f.tar.gz vis-c0e86f811b3a8e4f45768db86e97d1b0fda5616f.tar.xz | |
vis: overhaul input queue handling
Let vis_keys_feed always have an immediate effect. Previously,
if called from a key input handler the keys would just be added
to the input queue and processed once the current key handler
returned.
This also affects the exposed Lua API.
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 2 |
1 files changed, 1 insertions, 1 deletions
@@ -601,7 +601,7 @@ At this time there exists no API stability guarantees. - `motion(id)` select/execute a motion - `command_register(name, function(argv, force, win, cursor, range))` hook up a Lua function to `:name` command - `map(mode, key, function)` map a Lua function to `key` in `mode` - - `feedkeys(keys)` interpret `keys` as if they were read from the keyboard. If called from a key handling function, the keys will only be processed *after* the current key handling function has returned. + - `feedkeys(keys)` interpret `keys` as if they were read from the keyboard - `recording` boolean property, indicates whether a macro is currently being recorded - `file` - `content(pos, len)` or `content({start, finish})` |