diff options
| author | Bram Moolenaar <Bram@vim.org> | 2021-01-28 11:07:44 +0100 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2021-01-28 11:07:44 +0100 |
| commit | 2e6cdb91e8dea08301f31bc83188c06112eb7f57 (patch) | |
| tree | 7a036777bf8fc4db2e39c92ee1923c5c9953747c /src/edit.c | |
| parent | 3e492c2d5fbd4ae395ffddfc059a3c414604b951 (diff) | |
| download | vim-git-2e6cdb91e8dea08301f31bc83188c06112eb7f57.tar.gz | |
patch 8.2.2418: color not changed if ModeMsg highlight is set in InsertEnterv8.2.2418
Problem: Color not changed if ModeMsg highlight is set in InsertEnter
autocmd event. (Paul Swanson)
Solution: Call highlight_changed() after triggering InsertEnter.
(closes #7751)
Diffstat (limited to 'src/edit.c')
| -rw-r--r-- | src/edit.c | 4 |
1 files changed, 4 insertions, 0 deletions
diff --git a/src/edit.c b/src/edit.c index 35e4bc2c4..9162fe629 100644 --- a/src/edit.c +++ b/src/edit.c @@ -196,6 +196,10 @@ edit( #endif ins_apply_autocmds(EVENT_INSERTENTER); + // Check for changed highlighting, e.g. for ModeMsg. + if (need_highlight_changed) + highlight_changed(); + // Make sure the cursor didn't move. Do call check_cursor_col() in // case the text was modified. Since Insert mode was not started yet // a call to check_cursor_col() may move the cursor, especially with |