diff options
| author | Justin M. Keyes <justinkz@gmail.com> | 2019-05-09 19:35:38 +0200 |
|---|---|---|
| committer | Justin M. Keyes <justinkz@gmail.com> | 2019-05-09 22:27:41 +0200 |
| commit | b9ad12e6c2fa557e2c2c2f2f6c40fabc0cc89efd (patch) | |
| tree | e39da37c2dae8899bb9d18c07cc5861a942f72dc /runtime/doc/debug.txt | |
| parent | 8330cc22afec67d9dbc2ad8b4a39eaf62fdf16d1 (diff) | |
| download | rneovim-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 'runtime/doc/debug.txt')
| -rw-r--r-- | runtime/doc/debug.txt | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/runtime/doc/debug.txt b/runtime/doc/debug.txt index 1019becf9c..fab12e36fa 100644 --- a/runtime/doc/debug.txt +++ b/runtime/doc/debug.txt @@ -108,7 +108,7 @@ line numbers. Double-click one of the lines and the Find Source dialog will appear. Navigate to the directory where the Vim source is (if you have it.) If you don't know how to debug this any further, follow the instructions -at ":help bug-reports". Paste the call stack into the bug report. +at ":help bug-report". Paste the call stack into the bug report. If you have a non-free version of Visual Studio, you can save a minidump via the Debug menu and send it with the bug report. A minidump is a small file |