GNU bug report logs - #8890
23.3; message writing slows emacs

Previous Next

Full log

Message #80 received at 8890 <at> debbugs.gnu.org (full text, mbox):

From: Lars Magne Ingebrigtsen <larsi <at> gnus.org>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: Dave Abrahams <dave <at> boostpro.com>, 8890 <at> debbugs.gnu.org
Subject: Re: bug#8890: 23.3; message writing slows emacs
Date: Sun, 18 Sep 2011 08:50:24 +0200

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

>> If it's been less than (say) 50th of a second since the previous
>> message, then don't message anything.  However, set up a timer in a
>> 100th of a second's time to display that message -- if nothing else has
>> been displayed in the mean time.
>
> That's much too tricky to implement.  Making it reliable is going to
> be painful.

Is it getting a timer to work that's tricky?

> Much easier to allow progress-reporter-update to output non-percentage
> messages (e.g. for bytecomp, the changing part is not a percentage but
> a function name).

If we're not going to make `message' just behave, then a function pair
like `message-maybe' (which wouldn't output anything that arrives too
fast) and a `message-flush' (to say that we're finished with the dubious
messaging) might do the trick.

That doesn't work very well with nested regions of dubious messaging, of
course, but that's probably not very common.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.