Bug report--window driver 3.51 bogosity during window switch

[Michael "Ford" Ditto]

In article <4789 at cbmvax.UUCP> ditto at cbmvax.UUCP (Michael "Ford" Ditto) writes:
>       Switching windows causes a SIGWIND signal to be sent, apparrently to
>the whole process group.  Usually, this is harmless, but certain programs
>seem to be confused by this.  For example, if you bang out to a shell from
>the "less" program
 [ ... ]

I got out the source to less and discovered that it is explicitly catching
SIGWIND if it exists (so that it can find out if the window changes size
while it's running, although this doesn't seem to work).  Then the wait()
inside system() gets aborted by the signal.  That explains why less is
affected when other programs aren't, but still seems bogus.  Less could
ignore SIGWIND before calling system(), but then it wouldn't find out about
any window changes in the meantime.

Perhaps it should be considered a bug in the Unix PC's system() function,
since SIGWIND is a legitimate process-group-type signal that might occur,
but system() only takes care of SIGINT and SIGQUIT.
-- 
					-=] Ford [=-

	.		.		(In Real Life: Mike Ditto)
.	    :	       ,		ford at kenobi.cts.com
This space under construction,		...!ucsd!elgar!ford
pardon our dust.			ditto at cbmvax.cbm.commodore.com