From: Eli Zaretskii <eliz@gnu.org>
To: Glenn Morris <rgm@gnu.org>
Cc: michael_heerdegen@web.de, 10539@debbugs.gnu.org
Subject: bug#10539: 24.0.92; low display-time-interval makes Emacs slow
Date: Sat, 28 Jan 2012 22:28:53 +0200 [thread overview]
Message-ID: <838vkry3ju.fsf@gnu.org> (raw)
In-Reply-To: <mn7h0bmx5x.fsf@fencepost.gnu.org>
> From: Glenn Morris <rgm@gnu.org>
> Cc: michael_heerdegen@web.de, 10539@debbugs.gnu.org
> Date: Sat, 28 Jan 2012 14:42:18 -0500
>
> Eli Zaretskii wrote:
>
> > Would the following wording make it less confusing/contradictory?
> >
> > Force next redisplay cycle to update the current buffer's mode line
> > and header line, based on the latest values of all the relevant
> > variables.
>
> Yes thanks. Plus something similar for the function's doc-string.
Will do.
> So it doesn't actually "force redisplay", it just marks things to be
> updated the next time redisplay happens to occur (?).
Yes, exactly.
next prev parent reply other threads:[~2012-01-28 20:28 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=838vkry3ju.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=10539@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=rgm@gnu.org \
/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.