aboutsummaryrefslogtreecommitdiff
path: root/src/nvim/syntax.c
diff options
context:
space:
mode:
authorBjörn Linse <bjorn.linse@gmail.com>2018-09-20 12:06:19 +0200
committerBjörn Linse <bjorn.linse@gmail.com>2018-09-20 12:25:31 +0200
commit5487624730b60426632326dde41383069754916b (patch)
tree0c2470360fb196ba27a0aaeeca6fe077fa58f7aa /src/nvim/syntax.c
parent47d74bf32f3b95b28a3ef2a7840989eb9bed7480 (diff)
downloadrneovim-5487624730b60426632326dde41383069754916b.tar.gz
rneovim-5487624730b60426632326dde41383069754916b.tar.bz2
rneovim-5487624730b60426632326dde41383069754916b.zip
startup: don't erase screen on `:hi Normal` during startup
NB: existing `color default` test was actually enough to trigger the bug, when ext_newgrid=false is used. I created the `:hi Normal` test as I thought the builtin colors wouldn't set Normal (unless 'bg' is changed) But as the root cause actually comes from `:hi Normal`, it makes sense to still add the separate test (if `color default` here gets optimized to become a no-op, or something).
Diffstat (limited to 'src/nvim/syntax.c')
-rw-r--r--src/nvim/syntax.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/nvim/syntax.c b/src/nvim/syntax.c
index 05f06d64c3..4c054dc8e0 100644
--- a/src/nvim/syntax.c
+++ b/src/nvim/syntax.c
@@ -6884,7 +6884,7 @@ void do_highlight(const char *line, const bool forceit, const bool init)
// "fg", which have been changed now.
highlight_attr_set_all();
- if (!ui_is_external(kUINewgrid) && starting != NO_SCREEN) {
+ if (!ui_is_external(kUINewgrid) && starting == 0) {
// Older UIs assume that we clear the screen after normal group is
// changed
ui_refresh();