From: Lars Magne Ingebrigtsen <larsi@gnus.org>
To: Dave Abrahams <dave@boostpro.com>
Cc: 8890@debbugs.gnu.org
Subject: bug#8890: 23.3; message writing slows emacs
Date: Sat, 17 Sep 2011 07:19:56 +0200 [thread overview]
Message-ID: <m3zki3lp8j.fsf@stories.gnus.org> (raw)
In-Reply-To: <m2hb4co72b.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Fri, 16 Sep 2011 11:11:56 -0400")
Dave Abrahams <dave@boostpro.com> writes:
>> So the general approach to fixing those problems is to say "use
>> progress-reporter-update" since this function has the advantage of
>> knowing that there will be a `progress-reporter-done' at some later
>> point, which allows it to skip a message without worries.
>
> Hm. So there *is* a builtin functionality for this... well, that's
> good. Sorry if I've wasted everyone's time on this.
I didn't know about progress-reporter, so my time wasn't wasted, at
least. :-)
But I wonder whether a simpler, more general function would be
possible. If we're outputting stuff that's not a percentage,
progress-reporter doesn't help much.
`message' could work as follows:
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.
The net effect will be that normal messaging (where it's been a long
time since the previous message) is displayed as usual, but when we
enter a "high-message" storm, we start skipping messages. But we always
end up showing the final message, anyway.
This would be a very simple interface for programmers to deal with
(i.e., "don't worry about it"), and the user wouldn't notice anything in
particular -- other than Emacs being faster in some situations.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog http://lars.ingebrigtsen.no/
next prev parent reply other threads:[~2011-09-17 5:19 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-18 16:45 bug#8890: 23.3; message writing slows emacs Dave Abrahams
2011-09-11 4:32 ` Lars Magne Ingebrigtsen
2011-09-11 6:54 ` Dave Abrahams
2011-09-11 8:55 ` Eli Zaretskii
2011-09-11 10:45 ` Dave Abrahams
2011-09-11 11:20 ` Eli Zaretskii
2011-09-11 11:30 ` Dave Abrahams
2011-09-11 14:52 ` Lars Magne Ingebrigtsen
2011-09-11 15:58 ` Eli Zaretskii
2011-09-11 16:39 ` Dave Abrahams
2011-09-16 2:22 ` Dave Abrahams
2011-09-16 8:54 ` Eli Zaretskii
2011-09-11 14:51 ` Lars Magne Ingebrigtsen
2011-09-16 13:18 ` Stefan Monnier
2011-09-16 13:45 ` Eli Zaretskii
2011-09-16 14:20 ` Stefan Monnier
2011-09-16 15:11 ` Dave Abrahams
2011-09-17 5:19 ` Lars Magne Ingebrigtsen [this message]
2011-09-17 6:23 ` Dave Abrahams
2011-09-17 8:25 ` Eli Zaretskii
2011-09-17 8:29 ` Lars Magne Ingebrigtsen
2011-09-17 9:24 ` Eli Zaretskii
2011-09-17 12:01 ` Juri Linkov
2011-09-17 21:06 ` Stefan Monnier
2011-09-18 6:50 ` Lars Magne Ingebrigtsen
2011-09-18 13:16 ` Stefan Monnier
2011-09-21 19:01 ` Lars Magne Ingebrigtsen
2022-04-26 13:20 ` Lars Ingebrigtsen
2011-09-16 15:09 ` Dave Abrahams
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3zki3lp8j.fsf@stories.gnus.org \
--to=larsi@gnus.org \
--cc=8890@debbugs.gnu.org \
--cc=dave@boostpro.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.