unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 52332@debbugs.gnu.org, info@protesilaos.com
Subject: bug#52332: 29.0.50; Invisible button in the mode line
Date: Tue, 21 Dec 2021 14:21:12 +0200	[thread overview]
Message-ID: <83wnjyywqv.fsf@gnu.org> (raw)
In-Reply-To: <87a6gujzfc.fsf@gnus.org> (message from Lars Ingebrigtsen on Tue,  21 Dec 2021 06:32:23 +0100)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 52332@debbugs.gnu.org,  Protesilaos Stavrou <info@protesilaos.com>
> Date: Tue, 21 Dec 2021 06:32:23 +0100
> 
> By the way, I wanted to mention -- while poking at this stuff, I noticed
> that apparently the mode line is redisplayed multiple times when doing
> some common things.
> 
> For instance, hitting page-down seems to render the mode line twice?
> Mouse-clicking something also renders it twice.  Hm...  oh, it renders
> once on mouse-down and once on mouse-up, so I guess that's OK.  So I
> guess the only mysterious one is the page-down/page-up double render.

This is normal.  Scrolling commands first see if point is inside the
window, and that requires redisplay of the mode line (because its
spec could have changed in the meanwhile).  Then the scrolling
commands determine the appropriate window-start point, and then
redisplay kicks in with the second update of the mode line.





      reply	other threads:[~2021-12-21 12:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-06 16:40 bug#52332: 29.0.50; Invisible button in the mode line Protesilaos Stavrou
2021-12-06 17:11 ` Eli Zaretskii
2021-12-06 18:10   ` Protesilaos Stavrou
2021-12-06 18:28     ` Eli Zaretskii
2021-12-20 12:37       ` Lars Ingebrigtsen
2021-12-21  5:32         ` Lars Ingebrigtsen
2021-12-21 12:21           ` Eli Zaretskii [this message]

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=83wnjyywqv.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=52332@debbugs.gnu.org \
    --cc=info@protesilaos.com \
    --cc=larsi@gnus.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 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).