From: "Nicolas Bértolo" <nicolasbertolo@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 40278@debbugs.gnu.org
Subject: bug#40278: 27.0.90; Flickering in Windows 10
Date: Sun, 29 Mar 2020 17:58:51 -0300 [thread overview]
Message-ID: <CAFnS-OkMa+FrP8G1xNUwyvX0k_3wNTz4Dho0heygbmVAEaJDZA@mail.gmail.com> (raw)
In-Reply-To: <83y2rj3wfp.fsf@gnu.org>
> I don't see it.
I have found that creating a child frame causes it to flicker a lot more.
Here is a video that shows what happens https://youtu.be/BsUqPpyAvVQ
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.
I don't know if this is the same bug or if it's related.
El dom., 29 mar. 2020 a las 14:25, Eli Zaretskii (<eliz@gnu.org>) escribió:
>
> > Date: Sun, 29 Mar 2020 13:11:20 -0300
> > From: Nicolas Bertolo <nicolasbertolo@gmail.com>
> > Bcc: <nicolasbertolo@gmail.com>
> >
> > 1) Open a long C++ file.
> >
> > 2) Run (setq mouse-wheel-scroll-amount '(1)).
> >
> > 3) Mouse the mouse whell up and down fast.
> >
> > 4) Pay attention to the part of the screen that should show new content.
> >
> > Sometimes it will flicker a few time before stabilizing.
>
> I don't see it.
next prev parent reply other threads:[~2020-03-29 20:58 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 [this message]
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
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=CAFnS-OkMa+FrP8G1xNUwyvX0k_3wNTz4Dho0heygbmVAEaJDZA@mail.gmail.com \
--to=nicolasbertolo@gmail.com \
--cc=40278@debbugs.gnu.org \
--cc=eliz@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 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).