Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!husc6!cmcl2!beta!unm-la!unmvax!turing!mike From: mike@turing.unm.edu (Michael I. Bushnell) Newsgroups: comp.emacs Subject: Re: Termcap entries Message-ID: <586@unmvax.UNM.EDU> Date: Tue, 7-Jul-87 15:37:18 EDT Article-I.D.: unmvax.586 Posted: Tue Jul 7 15:37:18 1987 Date-Received: Fri, 10-Jul-87 06:03:19 EDT References: <583@unmvax.UNM.EDU> <8707071419.AA01369@ucbvax.Berkeley.EDU> Sender: news@unmvax.UNM.EDU Reply-To: mike@turing.UUCP (Michael I. Bushnell) Distribution: world Organization: University of New Mexico, Albuquerque Lines: 26 In article <8707071419.AA01369@ucbvax.Berkeley.EDU> jr@LF-SERVER-2.BBN.COM (John Robinson) writes: ~~~ 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. ~ ~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. ~ Thank you very much. I finally have an incentive. You see, when I first obtained GNUemacs, I found that there were problems with getting the X features to work. The problems were with our X installation, and have now been repaired. But I have been too lazy to recompile it. Michael I. Bushnell a/k/a Bach II mike@turing.UNM.EDU --- My haircut is totally traditional! -- Zippy the Pinhead