unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: 10539@debbugs.gnu.org
Subject: bug#10539: 24.0.92; low display-time-interval makes Emacs slow
Date: Sat, 23 Apr 2022 16:41:48 +0200	[thread overview]
Message-ID: <87o80rrheb.fsf@gnus.org> (raw)
In-Reply-To: <87zkdl93r0.fsf@web.de> (Michael Heerdegen's message of "Wed, 18 Jan 2012 02:52:03 +0100")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> The docstring of `display-time-interval' says "Seconds between updates
> of time in the mode line.".  Ok, fine.  The doc of
> `display-time-string-forms' includes an example which makes
> `display-time-mode' show seconds.  So, the user may think setting
> `display-time-interval' to 1 is a good idea.
>
> But it is currently not, on the contrary.
>
> First of all, `display-time-update' is a long, complex function.
> Running only its calculations every second consumes some percent CPU by
> itself.

(I'm going through old bug reports that unfortunately weren't resolved
at the time.)

I've tried this in Emacs 29, and the Emacs in question does not show up
on "top" as consuming any CPU, so this has perhaps improved?

> Second, the doc of `display-time-update' says
>
>   Update the display-time info for the mode line.
>   However, don't redisplay right now.
>
> But it _does_ redisplay, it calls `force-mode-line-update' explicitly at
> the end of the code!

As noted in the bug thread, `force-mode-line-update' just sets some
variables to make the next redisplay cycle update the mode lines, so
the doc string is correct, I think.

The discussion then went on to adding some more comments or something,
but I'm not sure whether there's anything more to be done here?

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





  parent reply	other threads:[~2022-04-23 14:41 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-18  1:52 bug#10539: 24.0.92; low display-time-interval makes Emacs slow Michael Heerdegen
2012-01-27 21:30 ` Glenn Morris
2012-01-28  8:40   ` Eli Zaretskii
2012-01-28 11:07     ` martin rudalics
2012-01-28 19:43       ` Glenn Morris
2012-01-28 19:42     ` Glenn Morris
2012-01-28 20:28       ` Eli Zaretskii
2012-01-28 20:51         ` Glenn Morris
2012-01-28 21:29           ` Eli Zaretskii
2012-01-29  6:07             ` Glenn Morris
2012-01-29 16:07               ` Drew Adams
2012-01-29 17:11               ` Eli Zaretskii
2012-01-30  4:40                 ` Stefan Monnier
2012-01-30 17:44                   ` Eli Zaretskii
2012-01-30 22:01                     ` Stefan Monnier
2012-01-31  3:48                       ` Eli Zaretskii
2012-01-29 17:51             ` martin rudalics
2012-01-29 18:26               ` Eli Zaretskii
2012-01-30 10:20                 ` martin rudalics
2012-01-30 18:02                   ` Eli Zaretskii
2012-01-30 18:13                     ` martin rudalics
2012-01-30 19:04                       ` Eli Zaretskii
2022-04-23 14:41 ` Lars Ingebrigtsen [this message]
2022-04-30  1:12   ` Michael Heerdegen
2022-04-30 11:46     ` Lars Ingebrigtsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87o80rrheb.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=10539@debbugs.gnu.org \
    --cc=michael_heerdegen@web.de \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).