patch 9.1.0047: issues with temp curwin/buf while cmdwin is open Commit: https://github.com/vim/vim/commit/988f74311c26ea9917e84fbae608de226dba7e5f Author: Sean Dewar <seandewar@users.noreply.github.com> Date: Wed Aug 16 14:17:36 2023 +0100 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>

/* XPM */
static char * vim16x16[] = {
"16 16 8 1",
" 	c None",
".	c #000000",
"+	c #000080",
"@	c #008000",
"#	c #00FF00",
"$	c #808080",
"%	c #C0C0C0",
"&	c #FFFFFF",
"  .....#. ....  ",
" .&&&&&.@.&&&&. ",
" .%%%%%$..%%%%$.",
"  .%%%$.@.&%%$. ",
"  .%%%$..&%%$.  ",
"  .%%%$.&%%$..  ",
" #.%%%$&%%$.@@. ",
"#@.%%%&%%$.@@@@.",
".@.%%%%%..@@@@+ ",
" ..%%%%.%...@.  ",
"  .%%%%...%%.%. ",
"  .%%%.%%.%%%%%.",
"  .%%$..%.%.%.%.",
"  .%$.@.%.%.%.%.",
"   .. .%%.%.%.%.",
"       .. . . . "};