unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40278@debbugs.gnu.org, "Nicolas Bértolo" <nicolasbertolo@gmail.com>
Subject: bug#40278: 27.0.90; Flickering in Windows 10
Date: Mon, 30 Mar 2020 12:23:42 -0400	[thread overview]
Message-ID: <85imilolpt.fsf@gmail.com> (raw)
In-Reply-To: <834ku63pj1.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 30 Mar 2020 17:06:58 +0300")


>> To reproduce it:
>> 1) Start runemacs -Q
>> 2) Open a big C/C++ file (I used dispextern.h from emacs)
>> 3) Run this code to create the child frame (in the scratch buffer)
>> 
>> (defun open-test ()
>>   (display-buffer-in-child-frame (get-buffer-create "test child-frame")
>>                    '((child-frame-parameters . ((width . 20)
>>                                                             (height . 10)
>>                                                             (top . 200)
>>                                                             (left . 100))))))
>> 4) In the C/C++ buffer eval (open-test)
>> 5) Scroll with the mouse wheel up and down.
>
> It doesn't flicker here, sorry.
>
> Does anyone else see this?

I can see it here, especially on scroll towards the beginning of the
file (Emacs is maxing out the CPU while doing this).  It kind of looks
like the rectangle beneath the child frame gets repainted separately
from the rest.

In GNU Emacs 27.0.90 (build 1, x86_64-w64-mingw32)
 of 2020-03-30 built on VHOST2
Repository revision: c6e0981b96eaa12c28b70c949ccd6e426c13df4d
Repository branch: emacs-27
Windowing system distributor 'Microsoft Corp.', version 10.0.18363
System Description: Microsoft Windows 10 Home (v10.0.1909.18363.720)





  reply	other threads:[~2020-03-30 16:23 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 [this message]
2020-03-30 16:40         ` Eli Zaretskii
2020-03-30 17:15           ` Noam Postavsky
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=85imilolpt.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).