Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!ll-xn!husc6!panda!teddy!jpn From: jpn@teddy.UUCP (John P. Nelson) Newsgroups: comp.sources.d,comp.terminals Subject: Re: VT100's keeping up at high baud rates Message-ID: <4117@teddy.UUCP> Date: Wed, 17-Jun-87 09:41:28 EDT Article-I.D.: teddy.4117 Posted: Wed Jun 17 09:41:28 1987 Date-Received: Sun, 21-Jun-87 09:26:18 EDT References: <1149@carthage.swatsun.UUCP> <8601@tekecs.TEK.COM> Reply-To: jpn@teddy.UUCP (John P. Nelson) Organization: GenRad, Inc., Concord, Mass. Lines: 19 Xref: mnetor comp.sources.d:861 comp.terminals:317 > While it's nice to >have a terminal that can keep up with 19200 without flow control (i.e. >continuous text display), that's approximately 19200 words per minute, and >neither you nor I nor Evelyn Wood's mother can read that fast over sustained >periods. The reasons you'd want a terminal to go that fast without flow >control are either that you use a braindamaged computer which can't handle it, >or that you're using EMACS, and flow control ^S puts you into search mode. Actually, we had a different reason. We were developing a software package which had to update the entire screen in response to a user's keystroke. Updating the screen at 1920 characters per second is MUCH snappier than updating the screen at 480 characters per second. Also, I found that is was much nicer to use any full screen editor at the faster speed. You were never waiting for the screen to be updated at a full 19200 baud. Of course the XOFF/XON issue is not the point: The point is "how fast can the terminal process display data". - john nelson