Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!decvax!ucbvax!ucbcad!nike!lll-crg!lll-lcc!pyramid!ut-sally!std-unix
From: std-unix@ut-sally.UUCP (Moderator, John Quarterman)
Newsgroups: mod.std.unix
Subject: Re: job control
Message-ID: <6003@ut-sally.UUCP>
Date: Tue, 14-Oct-86 12:42:39 EDT
Article-I.D.: ut-sally.6003
Posted: Tue Oct 14 12:42:39 1986
Date-Received: Wed, 15-Oct-86 00:55:18 EDT
Organization: IEEE P1003 Portable Operating System for Computer Environments Committee
Lines: 23
Approved: jsq@sally.utexas.edu

From: shannon@sun.com (Bill Shannon)
Date: Sun, 12 Oct 86 22:37:40 PDT

> From: cbosgd!cbosgd.ATT.COM!mark@seismo.css.gov (Mark Horton)
>
>	...
>
> (b) an ioctl to find out the current window size, in chars and pixels.

I've argued this with the people at Berkeley and lost, but I'll try
again here.  I don't believe there should be an ioctl to find out
the pixel size of a "window".  This seems to me to be the wrong way
to retrieve this information.  The pixel size is of no use to programs
that deal only in characters.  Only programs manipulating windows will
need to know the pixel size.  Whatever mechanism is used to manipulate
window should also be used to find out the pixel size of the window.
(Of course, this may be, but is not required to be, ioctl's.)  The tty
subsystem, which deals only in characters, should not know anything
about pixels or windows.

					Bill Shannon

Volume-Number: Volume 7, Number 57