startup: do "syntax enable" instead of "syntax on"

"syntax on" overwrites existing highlight groups, while "syntax enable"
just sets missing groups. This change prevents user defined highlights in
init.vim/lua to get overwritten. The manual recommends "syntax enable" for
new configurations anyway, "on" command was probably used as it is the
implicit default.
This commit is contained in:
Björn Linse
2021-04-14 11:02:43 +02:00
parent 59eae3b38f
commit b0a1d1eb64
2 changed files with 3 additions and 3 deletions

View File

@@ -375,7 +375,7 @@ int main(int argc, char **argv)
// Does ":filetype plugin indent on". // Does ":filetype plugin indent on".
filetype_maybe_enable(); filetype_maybe_enable();
// Sources syntax/syntax.vim, which calls `:filetype on`. // Sources syntax/syntax.vim, which calls `:filetype on`.
syn_maybe_on(); syn_maybe_enable();
} }
// Read all the plugin files. // Read all the plugin files.

View File

@@ -3469,13 +3469,13 @@ static void syn_cmd_onoff(exarg_T *eap, char *name)
} }
} }
void syn_maybe_on(void) void syn_maybe_enable(void)
{ {
if (!did_syntax_onoff) { if (!did_syntax_onoff) {
exarg_T ea; exarg_T ea;
ea.arg = (char_u *)""; ea.arg = (char_u *)"";
ea.skip = false; ea.skip = false;
syn_cmd_onoff(&ea, "syntax"); syn_cmd_enable(&ea, false);
} }
} }