forked from aniani/vim
patch 9.1.0047: issues with temp curwin/buf while cmdwin is open
Problem: Things that temporarily change/restore curwin/buf (e.g: win_execute, some autocmds) may break assumptions that curwin/buf is the cmdwin when "cmdwin_type != 0", causing issues. Solution: Expose the cmdwin's real win/buf and check that instead. Also try to ensure these variables are NULL if "cmdwin_type == 0", allowing them to be used directly in most cases without checking cmdwin_type. (Sean Dewar) Alternatively, we could ban win_execute in the cmdwin and audit all places that temporarily change/restore curwin/buf, but I didn't notice any problems arising from allowing this (standard cmdwin restrictions still apply, so things that may actually break the cmdwin are still forbidden). closes: #12819 Signed-off-by: Sean Dewar <seandewar@users.noreply.github.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
committed by
Christian Brabandt
parent
4927110a43
commit
988f74311c
@@ -1087,7 +1087,7 @@ fold_line(
|
||||
|
||||
// 1. Add the cmdwin_type for the command-line window
|
||||
// Ignores 'rightleft', this window is never right-left.
|
||||
if (cmdwin_type != 0 && wp == curwin)
|
||||
if (wp == cmdwin_win)
|
||||
{
|
||||
ScreenLines[off] = cmdwin_type;
|
||||
ScreenAttrs[off] = HL_ATTR(HLF_AT);
|
||||
|
Reference in New Issue
Block a user