Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!bbn!jr@bbn.com From: jr@bbn.com (John Robinson) Newsgroups: comp.emacs Subject: Re: Visual searching Message-ID: <39384@bbn.COM> Date: 2 May 89 20:41:31 GMT References: <192@dftsrv.gsfc.nasa.gov> <58989@yale-celray.yale.UUCP> Sender: news@bbn.COM Reply-To: jr@bbn.com (John Robinson) Distribution: na Organization: BBN Systems and Technologies Corporation, Cambridge MA Lines: 31 In-reply-to: hedrick@geneva.rutgers.edu (Charles Hedrick) In article , hedrick@geneva (Charles Hedrick) writes: >I find the whole idea of terminals that issue XOFF unacceptable, but >DEC seems to have started it with the VT100. They really sealed the fate with the VT101 (or was it -102?). That beast not only couldn't keep up at 4800 baud, if you sent it nulls (or whatever) as padding it still spent so much time throwing away the padding that it fell further behind. No amount of padding worked; you *had* to use real delays (which not many terminal drivers support, and which is useless across any sort of network). > My recommendation is that >you leave XON/XOFF turned on in the terminal, and modify termcap so >that there is enough padding that XON/XOFF are never actually >generated. Then when you are outside emacs (and other programs that >use termcap), XON/XOFF will work, but when you go into a program that >uses termcap, you'll get enough padding that XON is never triggered. You still need to learn how to map other keys to ^S and ^Q so you can search and quote, since typing these characters will generally be impossible on terminals that insist on flow control. It is also a bug that some terminals don't let you turn flow control on and off with an escape sequence, the way they do, say, reverse-video. Recent postings about the keyboard-translate-table talk about remapping keys. (or write me if you really need this and can't find it in your manual or info or help files). -- /jr jr@bbn.com or bbn!jr C'mon big money!