Xref: utzoo gnu.emacs.help:304 comp.emacs:9489
Path: utzoo!utgpu!watserv1!watmath!uunet!tut.cis.ohio-state.edu!AI.MIT.EDU!rms
From: rms@AI.MIT.EDU (Richard Stallman)
Newsgroups: gnu.emacs.help,comp.emacs
Subject: command idea
Message-ID: <9011112032.AA12853@mole.ai.mit.edu>
Date: 11 Nov 90 20:32:08 GMT
References: <JWZ.90Nov9224044@kolyma.lucid.com>
Sender: daemon@tut.cis.ohio-state.edu
Followup-To: gnu.emacs.help
Organization: GNUs Not Usenet
Lines: 18


   Date: 10 Nov 90 06:40:44 GMT
   From: jwz@lucid.com  (Jamie Zawinski)
   Organization: Lucid, Inc., Menlo Park, CA
   References: <9011100445.AA02007@albert.ai.mit.edu>
   Sender: help-gnu-emacs-request@prep.ai.mit.edu

   In article <9011100445.AA02007@albert.ai.mit.edu> roland@AI.MIT.EDU (Roland McGrath) wrote:
   > 
   > That sounds odd.  Emacs's redisplay is pretty smart.  Does it know what
   > speed you're at?  Try "stty 1200" before starting Emacs.

   Been there, done that.  (baud-rate) returns 1200.  I'm going through a
   terminal concentrator, but that shouldn't matter if emacs is pushing
   characters exactly at the speed of the line, which it doesn't seem to be
   doing.

There is already code in dispnew.c to do this.