Path: utzoo!utgpu!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!zaphod.mps.ohio-state.edu!uakari.primate.wisc.edu!sdd.hp.com!think.com!rpi!uupsi!ficc!peter From: peter@ficc.ferranti.com (Peter da Silva) Newsgroups: comp.dcom.modems Subject: Re: T1000 Message-ID: <.D6B0O7@xds13.ferranti.com> Date: 9 May 91 14:42:26 GMT References: <35@mich-ns.Michigan.COM> <1991May3.013332.7385@sugra.uucp> <1991May8.185155.2818@qualcomm.com> Reply-To: peter@ficc.ferranti.com (Peter da Silva) Organization: Xenix Support, FICC Lines: 34 In article <1991May8.185155.2818@qualcomm.com> rdippold@cancun.qualcomm.com (Ron Dippold) writes: > * Quickscan.. I can usually tell immediately after a message starts appearing > whether or not I'm interested. On 2400 I have to wait a lot longer to > junk it. Use "vnews" or another reader that allows hotkeys. > * Continuity - I can scan a static screen a lot faster than I can one which > is moving. Then use "vnews", or set your terminal to smooth scroll. I find the opposite to be true (so Emacs drives me up the wall with its page flipping). > * Headers - there's about 8+ lines of header information up there that for > most messages I don't really care about, but which takes up quite a bit of > time at 2400 bps. Software problem. Use a newsreader that hides that stuff. > * .signatures... some scum (usually on the debate bases) have 12-14, even > full screen sigs! See above. User interface problem. > * Editing... if you want to use vi to edit your replies and cut down the > quoted text, its a lot slower at 2400. Let me let you in on a secret: when VI was designed at Berkeley the *fast* terminals were running at 1200 and 2400 baud. Most terminals were 110 or 300 baud. VI is *designed* for slow terminals, and is quite usable on them if you set it up right. -- Peter da Silva; Ferranti International Controls Corporation; +1 713 274 5180; Sugar Land, TX 77487-5012; `-_-' "Have you hugged your wolf, today?"