diff options
author | Erik S. V. Jansson <caffeineviking@gmail.com> | 2024-02-24 14:26:52 +0100 |
---|---|---|
committer | Christian Brabandt <cb@256bit.org> | 2024-02-24 14:26:52 +0100 |
commit | 8b1e749ca6ca6d09a174c57de6999f69393ee567 (patch) | |
tree | 63e1d835d7753947d548af6b744fa674164dae5e /src/testdir/test_gui.vim | |
parent | 048761bcd40ec630fd3e039f0066cf4e484ceabd (diff) |
patch 9.1.0133: MS-Windows: ligatures not rendering correctlyv9.1.0133
Problem: font ligatures don't render correctly in the Win32 GUI-version
of gvim even when set rop=type:directx is used. Setting
guiligatures also doesn't make any difference. This leads to
broken font ligatures when the cursor passes through them. It
does not recover from this, and they remain broken until you
re-render the whole buffer (e.g. by using Ctrl+L).
Solution: the problem is that we only re-draw the current and previous
character in gui_undraw_cursor() and only have the special case
for GTK when it comes to rendering ligatures. So let's enable
gui_adjust_undraw_cursor_for_ligatures() to also happen for
Win32 GUI if guiligatures is setup correctly (all this does is
expand the range of gui_undraw_cursor() with ligature characters).
related: #9181
related: #12901
closes: #14084
Signed-off-by: Erik S. V. Jansson <caffeineviking@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
Diffstat (limited to 'src/testdir/test_gui.vim')
-rw-r--r-- | src/testdir/test_gui.vim | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/testdir/test_gui.vim b/src/testdir/test_gui.vim index dbf1d3b310..2ff8d3400b 100644 --- a/src/testdir/test_gui.vim +++ b/src/testdir/test_gui.vim @@ -635,7 +635,7 @@ endfunc func Test_set_guiligatures() CheckX11BasedGui - if has('gui_gtk') || has('gui_gtk2') || has('gui_gnome') || has('gui_gtk3') + if has('gui_gtk') || has('gui_gtk2') || has('gui_gnome') || has('gui_gtk3') || has('win32') " Try correct value set guiligatures=<>=ab call assert_equal("<>=ab", &guiligatures) |