Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!think.com!barmar From: barmar@think.com (Barry Margolin) Newsgroups: comp.unix.ultrix Subject: Re: Ultrix/X Message-ID: <1991Jan3.052827.27911@Think.COM> Date: 3 Jan 91 05:28:27 GMT References: <1991Jan3.042524.20774@crl.dec.com> Sender: news@Think.COM Organization: Thinking Machines Corporation, Cambridge MA, USA Lines: 25 In article <1991Jan3.042524.20774@crl.dec.com> jg@quabbin.crl.dec.com (Jim Gettys) writes: >In article bglenden@colobus.cv.nrao.edu (Brian Glendenning) writes: >>2. I tried compiling twm from X11R3. It apparently compiled fine, but my >> keystrokes never got to the application (but the border >> highlighting did follow the pointer). What have I done wrong? >This did not get adopted as a standard until R4, and software that >predates the ICCCM may have problems, ... >I suspect this is what is happening to your R3 twm; I certainly don't see it >with the R4 twm I use every day on my machine. Actually, it sounds like an R3 TWM bug that hit me quite a bit. If the .twmrc binds any keys that don't exist on the terminal you're using, no keyboard input is ever sent to client windows. Most users never noticed it, but if you switched between different terminals with different special function keys, and tried to bind actions to keys that they don't have in common, the problem rears its head. The workaround was to have multiple .twmrc files and rename them prior to starting twm. -- Barry Margolin, Thinking Machines Corp. barmar@think.com {uunet,harvard}!think!barmar