Path: utzoo!utgpu!water!watmath!uunet!cbmvax!ditto From: ditto@cbmvax.UUCP (Michael "Ford" Ditto) Newsgroups: unix-pc.bugs Subject: Re: Bug report--window driver 3.51 bogosity during window switch Summary: Other bizarre effects ... Keywords: bogus input flushing and signal sending Message-ID: <4789@cbmvax.UUCP> Date: 21 Sep 88 07:18:34 GMT References: <10552@stb.UUCP> <761@rush.cts.com> <10581@stb.UUCP> Reply-To: ditto@cbmvax.UUCP (Michael "Ford" Ditto) Organization: Commodore Technology, West Chester, PA Lines: 24 In article <10552@stb.UUCP>, michael@stb.UUCP (Michael) writes: > Problem: When windows are switched, the window that was active has all of > its keyboard input flushed. I don't like this even if it is documented, and speaking of stupid things that happen when you switch windows, there's another one that I can't stand. 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 (type "!sh"), and then switch windows, less will think the shell has exited and start reading the keyboard again. This results in a big mess. I haven't figured out why less is affected by this other than to observe that the wait(2) call within system(3) is returning early with errno==EINTR. This makes sense in itself, but obviously not all programs are affected in this way, and I don't think less should be either. -- -=] Ford [=- . . (In Real Life: Mike Ditto) . : , ford@kenobi.cts.com This space under construction, ...!ucsd!elgar!ford pardon our dust. ditto@cbmvax.commodore.com