aboutsummaryrefslogtreecommitdiff
path: root/scripts/gen_vimdoc.py
diff options
context:
space:
mode:
authorJustin M. Keyes <justinkz@gmail.com>2019-05-09 19:35:38 +0200
committerJustin M. Keyes <justinkz@gmail.com>2019-05-09 22:27:41 +0200
commitb9ad12e6c2fa557e2c2c2f2f6c40fabc0cc89efd (patch)
treee39da37c2dae8899bb9d18c07cc5861a942f72dc /scripts/gen_vimdoc.py
parent8330cc22afec67d9dbc2ad8b4a39eaf62fdf16d1 (diff)
downloadrneovim-b9ad12e6c2fa557e2c2c2f2f6c40fabc0cc89efd.tar.gz
rneovim-b9ad12e6c2fa557e2c2c2f2f6c40fabc0cc89efd.tar.bz2
rneovim-b9ad12e6c2fa557e2c2c2f2f6c40fabc0cc89efd.zip
UI/nvim_ui_attach(): add `override` option
Before now, Nvim always degrades UI capabilities to the lowest-common denominator. For example, if any connected UI has `ext_messages=false` then `ext_messages=true` requested by any other connected UI is ignored. Now `nvim_ui_attach()` supports `override=true`, which flips the behavior: if any UI requests an `ext_*` UI capability then the capability is enabled (and the legacy behavior is disabled). Legacy UIs will be broken while a `override=true` UI is connected, but it's useful for debugging: you can type into the TUI and observe the UI events from another connected (UI) client. And the legacy UI will "recover" after the `override=true` UI disconnects. Example using pynvim: >>> n.ui_attach(2048, 2048, rgb=True, override=True, ext_multigrid=True, ext_messages=True, ext_popupmenu=True) >>> while True: n.next_message();
Diffstat (limited to 'scripts/gen_vimdoc.py')
0 files changed, 0 insertions, 0 deletions