Mercurial > vim
view src/toolcheck @ 31471:eb7a266c6835 v9.0.1068
patch 9.0.1068: no information about whether request term codes has an effect
Commit: https://github.com/vim/vim/commit/8d754fada81df8d65ca6b9ebab72db71bfe5fd94
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Dec 17 13:49:16 2022 +0000
patch 9.0.1068: no information about whether request term codes has an effect
Problem: No information about whether requesting term codes has an effect.
Solution: Add ch_log() calls to report the effect of term code responses.
Avoid deleting an entry and then adding back the same one.
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 17 Dec 2022 15:00:03 +0100 |
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