Path: utzoo!attcan!uunet!ginosko!uakari.primate.wisc.edu!ames!haven!mimsy!chris From: chris@mimsy.UUCP (Chris Torek) Newsgroups: comp.unix.questions Subject: Re: Termcap needed for tektronix 4025 Message-ID: <19913@mimsy.UUCP> Date: 1 Oct 89 06:22:37 GMT References: <1989Sep28.165050.5839@uunet!unhd> <11192@smoke.BRL.MIL> Organization: U of Maryland, Dept. of Computer Science, Coll. Pk., MD 20742 Lines: 35 (What is this doing in comp.unix.questions? It belongs in comp.terminals. However, followups are now unlikely, so I have not redirected it there.) In article <11192@smoke.BRL.MIL> gwyn@smoke.BRL.MIL (Doug Gwyn) writes: >The Tek4025 is without doubt one of the most poorly designed terminals >ever made. Indeed. I have another 4025 termcap, but yours should do the job. Note that the one completely impossible `feature' of the 4025---there is no workaround, short of rewriting the ROM code---is that it confuses keyboard input with computer input during `escape' sequences. That is, if the computer sends ^]rig 23\r to send the cursor right 23 characters, and you happen to press the `l' key while that sequence is working its way across the RS232 cable into the 4025, the 4025 will imagine that the computer sent something like ^]rlig 23\r which either has no effect, or else prints `rlig 23' (I cannot recall which). This `feature' causes trouble more often at low baud rates%, so it is best to keep the 4025 connected at 9600 baud (although it can only write characters to the screen at around 400 per second, it uses all available memory for incoming data, so flow control is rarely a problem). ----- % At 1200 baud, an 8-character sequence takes .067 seconds, giving an `error window' 8 times larger than at 9600 baud (.0083 seconds). -- In-Real-Life: Chris Torek, Univ of MD Comp Sci Dept (+1 301 454 7163) Domain: chris@cs.umd.edu Path: uunet!mimsy!chris