Path: utzoo!utgpu!water!watmath!uunet!lll-winken!killer!gladys!bakerst!ihtlt!kosman!srhqla!denwa!stb!michael From: michael@stb.UUCP (Michael) Newsgroups: unix-pc.bugs Subject: Re: Bug report--window driver 3.51 Message-ID: <10581@stb.UUCP> Date: 11 Sep 88 23:07:12 GMT References: <10552@stb.UUCP> <761@rush.cts.com> Reply-To: michael@stb.UUCP (Michael) Organization: STB BBS, La, Ca, Usa, +1 213 459 7231 Lines: 28 In article <761@rush.cts.com> bob@rush.cts.com (Bob Ames) writes: >In article <10552@stb.UUCP>, michael@stb.UUCP (Michael) writes: >> Bug report, window driver 3.51. >> Problem: When windows are switched, the window that was active has all of >> its keyboard input flushed. > >I consider this a feature. This feature was included in all UNIX PC releases Well, I don't. It has the following effects: #1. Ctrl-s is lost when you change windows #2. If you type part of a command, switch windows to check the file name in another window, and then go back, there is a command line there that you typed but the system ignores. Now, the key was being remembered across window changes? You mean if you hit it fast enough, then when you re-enabled the window, that the window manager redisplayed its choice window? Or do you mean that hitting shift-susp fast enough caused the window to have a "stored next window" that activated the next time it was the active window. Both of these sound like window manager bugs to me. (After all, it is the one that receives the susp keys) Michael : --- : Michael Gersten uunet.uu.net!denwa!stb!michael : sdcsvax!crash!gryphon!denwa!stb!michael : Coff Coff <=== Stop smoking.