aboutsummaryrefslogtreecommitdiff
path: root/scripts/shadacat.py
diff options
context:
space:
mode:
authorBjörn Linse <bjorn.linse@gmail.com>2018-02-23 13:08:13 +0100
committerBjörn Linse <bjorn.linse@gmail.com>2018-02-24 09:10:00 +0100
commite18177692ab48e5ffc0c11184c723a52eed1248e (patch)
tree3f1d31a1fdcf226a560c2e2eaf171ad1af902e49 /scripts/shadacat.py
parentf3f1970597211c784190c4a1e1990d2386ac76a1 (diff)
downloadrneovim-e18177692ab48e5ffc0c11184c723a52eed1248e.tar.gz
rneovim-e18177692ab48e5ffc0c11184c723a52eed1248e.tar.bz2
rneovim-e18177692ab48e5ffc0c11184c723a52eed1248e.zip
screen.c: make negative 'writedelay' show all redraws
Currently writedelay shows the sequence of characters that are sent to the UI/TUI module. Here nvim has already applied an optimization: when attempting to put a char in a screen cell, if the same char already was there with the same attributes, UI output is disabled. When debugging redrawing it it sometimes more useful to inspect the redraw stream one step earlier, what region of the screen nvim actually is recomputing from buffer contents (win_line) and from evaluating statusline expressions. Take the popupmenu as an example. When closing the popupmenu (in the TUI), currently 'writedelay' looks like vim only is redrawing the region which the pum covered. This is not what happens internally: vim redraws the entire screen, even if only outputs the changed region. This commit allows negative values of 'writedelay', which causes a delay for all redrawn characters, even if the character already was displayed by the UI before.
Diffstat (limited to 'scripts/shadacat.py')
0 files changed, 0 insertions, 0 deletions