Date: Sat, 13 Jul 1996 02:10:04 -0700 (PDT) From: J Wunsch <j@uriah.heep.sax.de> To: freebsd-bugs Subject: Re: bin/1381: /bin/csh doesn't handle SIGWINCH correctly Message-ID: <199607130910.CAA25203@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR bin/1381; it has been noted by GNATS. From: J Wunsch <j@uriah.heep.sax.de> To: roberto@keltia.freenix.fr Cc: FreeBSD-gnats-submit@freebsd.org Subject: Re: bin/1381: /bin/csh doesn't handle SIGWINCH correctly Date: Sat, 13 Jul 1996 09:24:11 +0200 (MET DST) As Ollivier Robert wrote: > /bin/csh as shipped in 2.2-CURRENT (and probably 2.1-STABLE and the > forthcoming 2.1.5-RELEASE) doesn't support or is bug in its SIGWINCH > handling. Windows size changes are not shown in the environment, resulting > in problems with many programs. This is a non-bug. Shells are not supposed to intercept SIGWINCH for the purpose of fiddling with incorrect TERMCAP values. (Heck, the TERMCAP entry in the environment is even a rather useless invention.) li# and co# in the TERMCAP are a design error for terminals that can handle more than one size (i.e., for everything more recent than a VT100 or ADM3A). The correct way for programs to handle this is to examine the struct winsize, which is correctly updated, at least for cases like xterm or vty's. Of course, struct winsize is a design error. :-) It doesn't get notified when you turn your VT220 into 132-column mode manually. The entire tty capabilities' handling is a design error. :-)) Read the ``UNIX haters handbook'' for a more detailed explanation. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199607130910.CAA25203>