Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!decvax!decwrl!amdcad!lll-crg!seismo!ut-sally!std-unix From: std-unix@ut-sally.UUCP Newsgroups: mod.std.unix Subject: Re: job control Message-ID: <6025@ut-sally.UUCP> Date: Fri, 17-Oct-86 11:11:29 EDT Article-I.D.: ut-sally.6025 Posted: Fri Oct 17 11:11:29 1986 Date-Received: Fri, 17-Oct-86 21:16:22 EDT References: <5986@ut-sally.UUCP> <5932@ut-sally.UUCP> <5990@ut-sally.UUCP> <6004@ut-sally.UUCP> Organization: IEEE P1003 Portable Operating System for Computer Environments Committee Lines: 22 Approved: jsq@sally.utexas.edu From: bobr@zeus.UUCP (Robert Reed) Organization: CAE Systems Division, Tektronix Inc., Beaverton OR In article <6004@ut-sally.UUCP> Larry Campbell writes: > Of course programs should (and most do) query termcap/terminfo. However, > they can safely assume that the window size isn't going to change while > they're running, and this assumption reduces complexity. Programs cannot safely assume that window size is not going to change, because on most overlapped window management systems it will. It is just too easy to set inappropriate window sizes and then need to adjust them. Consider creating a new which is almost the right size (say 75 characters wide) and then invoking an editor on a file of 80 character data. The editor will either wrap or truncate the data, and changing the window size to compensate will do nothing but frustate the user. What is needed is something like 4.3 BSD's WINCH signal, to advise those applications which care about such changes. -- Robert Reed, Tektronix CAE Systems Division, bobr@zeus.TEK Volume-Number: Volume 7, Number 65