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>

#!/bin/sh
# toolcheck -- check for tools that have severe bugs. Good that all the buggy
#	       tools identify by version numbers. This is the spirit of GNU :-)
#
# 24.7.95 jw.

retval=0
reply="`sh -version -c exit 2>&1 < /dev/null`"
case "$reply" in
	GNU*1.14.3*)
		echo "- sh is	'$reply'";
		echo "  CAUTION: This shell has a buggy 'trap' command.";
		echo "           The configure script may fail silently.";
		retval=1;
		;;
	GNU*)
		echo "- sh is	'$reply' - probably OK.";
		;;
	*)	;;
esac

reply="`sed --version 2>&1 < /dev/null`"
case "$reply" in
	GNU\ sed\ version\ 2.0[34])
		echo "- sed is	'$reply'";
		echo "  CAUTION: This sed cannot configure screen properly."
		retval=1;
		;;
	GNU\ sed\ version\ 2.05|GNU\ sed\ version\ 2.03\ kevin)
		echo "- sed is	'$reply' - good.";
		;;
	GNU*)	echo "- sed is	'$reply'.";
		;;
	*)	;;
esac
exit $retval