From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40278@debbugs.gnu.org, nicolasbertolo@gmail.com
Subject: bug#40278: 27.0.90; Flickering in Windows 10
Date: Mon, 30 Mar 2020 13:15:39 -0400 [thread overview]
Message-ID: <85ftdpojb8.fsf@gmail.com> (raw)
In-Reply-To: <83o8sd3ifz.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Mar 2020 19:40:00 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> From: Noam Postavsky <npostavs@gmail.com>
>> Cc: Nicolas Bértolo <nicolasbertolo@gmail.com>,
>> 40278@debbugs.gnu.org
>> Date: Mon, 30 Mar 2020 12:23:42 -0400
>>
>> I can see it here, especially on scroll towards the beginning of the
>> file (Emacs is maxing out the CPU while doing this).
>
> If redisplay cannot keep up, you could indeed see partially-redrawn
> window. But I didn't understand this was the problem, and it doesn't
> sound like "flicker" to me.
The "flicker" part is that it looks like the window turns momentarily
completely blank before redrawing.
>> It kind of looks like the rectangle beneath the child frame gets
>> repainted separately from the rest.
>
> What do you mean by "beneath" in this context?
There's occasionally a rectangle which seems to repainted slower than
its surroundings. That rectangle is lower down (closer to my desk than
the ceiling) on my monitor than the child frame. Also, I guess the text
it momentarily contains was previously behind the child frame in terms
of z-order (although it's a bit hard to tell because the repainting is
still too fast to really anything).
next prev parent reply other threads:[~2020-03-30 17:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 16:11 bug#40278: 27.0.90; Flickering in Windows 10 Nicolas Bertolo
2020-03-29 17:25 ` Eli Zaretskii
2020-03-29 20:28 ` Nicolas Bértolo
2020-03-29 20:58 ` Nicolas Bértolo
2020-03-30 14:06 ` Eli Zaretskii
2020-03-30 16:23 ` Noam Postavsky
2020-03-30 16:40 ` Eli Zaretskii
2020-03-30 17:15 ` Noam Postavsky [this message]
2020-03-30 18:29 ` Eli Zaretskii
2020-03-30 19:21 ` Noam Postavsky
2020-03-31 8:48 ` martin rudalics
2020-03-31 15:51 ` Nicolas Bértolo
2020-03-31 15:56 ` Eli Zaretskii
2020-03-31 16:10 ` Nicolas Bértolo
2020-04-01 6:36 ` martin rudalics
2020-04-01 14:25 ` Noam Postavsky
2020-04-01 20:39 ` Nicolas Bértolo
2022-05-16 11:52 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=85ftdpojb8.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=40278@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=nicolasbertolo@gmail.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 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).