view src/toolcheck @ 14097:db44cd9f8068 v8.1.0066

patch 8.1.0066: nasty autocommand causes using freed memory commit https://github.com/vim/vim/commit/c3ffc9b8d3015dc5280b297b4e3deb4f34944bd4 Author: Bram Moolenaar <Bram@vim.org> Date: Sun Jun 17 17:32:58 2018 +0200 patch 8.1.0066: nasty autocommand causes using freed memory Problem: Nasty autocommand causes using freed memory. (Dominique Pelle) Solution: Do not force executing autocommands if the value of 'syntax' or 'filetype' did not change.
author Christian Brabandt <cb@256bit.org>
date Sun, 17 Jun 2018 17:45:05 +0200
parents 3fc0f57ecb91
children
line wrap: on
line source

#!/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