From: Eli Zaretskii <eliz@gnu.org>
To: martin rudalics <rudalics@gmx.at>
Cc: triska@metalevel.at, 52666@debbugs.gnu.org
Subject: bug#52666: 27.0.50; Unexpected mode line flickering when creating frames
Date: Wed, 22 Dec 2021 15:37:17 +0200 [thread overview]
Message-ID: <83ilvgyd4i.fsf@gnu.org> (raw)
In-Reply-To: <1557a1b7-f634-3add-5dde-6326b0b74328@gmx.at> (message from martin rudalics on Wed, 22 Dec 2021 10:22:57 +0100)
> Cc: Eli Zaretskii <eliz@gnu.org>, 52666@debbugs.gnu.org
> From: martin rudalics <rudalics@gmx.at>
> Date: Wed, 22 Dec 2021 10:22:57 +0100
>
> > 39.2 Forcing Redisplay
> > ======================
> >
> > Emacs normally tries to redisplay the screen whenever it waits for
> > input.
> >
> > In the example that exhibits the flickering, there is no waiting for
> > input between the creation of the frame and the change of its width and
> > height.
>
> Maybe that line is confusing.
Not really. It says "normally", and that is accurate. There are
other situations where Emacs does redisplay, either because some Lisp
program forced it to do so, or for other reasons.
The ELisp manual has limitations if treated as documentation of the
Emacs internals -- that's not its purpose.
> Emacs may have to redisplay whenever it
> receives a corresponding event (like Map, Visibility, Expose and Focus
> notifications). Waiting for user input is only a tangential aspect
> there.
Not entirely, or at least not always: Emacs ("normally") reads events
when it waits for input.
next prev parent reply other threads:[~2021-12-22 13:37 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-19 20:42 bug#52666: 27.0.50; Unexpected mode line flickering when creating frames Markus Triska
2021-12-20 9:18 ` martin rudalics
2021-12-20 15:11 ` Eli Zaretskii
2021-12-20 17:21 ` martin rudalics
2021-12-20 18:23 ` Markus Triska
2021-12-20 18:30 ` martin rudalics
2021-12-20 18:41 ` Markus Triska
2021-12-21 10:32 ` martin rudalics
2021-12-21 20:44 ` Markus Triska
2021-12-22 9:22 ` martin rudalics
2021-12-22 13:37 ` Eli Zaretskii [this message]
2021-12-22 16:33 ` Markus Triska
2021-12-23 14:46 ` martin rudalics
2021-12-23 16:23 ` Markus Triska
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=83ilvgyd4i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=52666@debbugs.gnu.org \
--cc=rudalics@gmx.at \
--cc=triska@metalevel.at \
/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).