Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!ptsfa!ames!ucbcad!ucbvax!LF-SERVER-2.BBN.COM!jr From: jr@LF-SERVER-2.BBN.COM.UUCP Newsgroups: comp.emacs Subject: Re: Termcap entries Message-ID: <8707071419.AA01369@ucbvax.Berkeley.EDU> Date: Tue, 7-Jul-87 10:22:09 EDT Article-I.D.: ucbvax.8707071419.AA01369 Posted: Tue Jul 7 10:22:09 1987 Date-Received: Thu, 9-Jul-87 02:30:04 EDT References: <583@unmvax.UNM.EDU> Sender: daemon@ucbvax.BERKELEY.EDU Distribution: world Organization: The ARPA Internet Lines: 24 >> Does anyone have a good termcap for xterms/xterm? The one with X does >> not accurately express the time for various operations, so that >> scrolls are done when repaints would be faster. Um, to do this, you need to know the "baud" rate of your xterm window, since the calculations are all based on the speed to send a character to the "terminal". With xterm, these concepts are silly, hence the quotes. You can set (with stty) the "baud" rate to anything you want; try playing with it to get the effect you want. Most systems have to pick a default for network connections; for xterm "connections" you should probably set it as fast as possible (and it would still be too slow). Since you are running X, why not use the built-in X support in emacs (oops, you didn't say which emacs. This applies only to GNU.)? This just forgets about the cost computation and sends updates all the time. Keeps xterm out of your way, and clears out your workstation's memory of that largish program to boot. Works especially nicely when your emacs is on a different host from your X. If you still have to modify the termcap, you should just probably remove the scroll/insert line/delete line capabilities. /jr