view src/toolcheck @ 16720:9c90cf08cfa8 v8.1.1362

patch 8.1.1362: code and data in tests can be hard to read commit https://github.com/vim/vim/commit/c79745a82faeb5a6058e915ca49a4c69fa60ea01 Author: Bram Moolenaar <Bram@vim.org> Date: Mon May 20 22:12:34 2019 +0200 patch 8.1.1362: code and data in tests can be hard to read Problem: Code and data in tests can be hard to read. Solution: Use the new heredoc style. (Yegappan Lakshmanan, closes https://github.com/vim/vim/issues/4400)
author Bram Moolenaar <Bram@vim.org>
date Mon, 20 May 2019 22:15:06 +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