unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: "Nicolas Bértolo" <nicolasbertolo@gmail.com>
Cc: 40278@debbugs.gnu.org, martin rudalics <rudalics@gmx.at>,
	Eli Zaretskii <eliz@gnu.org>, Noam Postavsky <npostavs@gmail.com>
Subject: bug#40278: 27.0.90; Flickering in Windows 10
Date: Mon, 16 May 2022 19:52:52 +0800	[thread overview]
Message-ID: <87tu9pofsb.fsf@yahoo.com> (raw)
In-Reply-To: <CAFnS-Ok1zQESas9TvW1THcgKC5F=_dxSg8_VEmT67CjTAbv+Dw@mail.gmail.com> ("Nicolas Bértolo"'s message of "Wed, 1 Apr 2020 17:39:06 -0300")

Nicolas Bértolo <nicolasbertolo@gmail.com> writes:

>> At any rate, if I've understood the responses from Eli, it sounds like
>> there isn't any bug here, just that we haven't implemented double
>> buffering for Windows.
>
> This may be the reason indeed.

So now that double buffering is implemented for MS Windows, do you still
see the flicker?





      reply	other threads:[~2022-05-16 11:52 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
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 [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=87tu9pofsb.fsf@yahoo.com \
    --to=bug-gnu-emacs@gnu.org \
    --cc=40278@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=luangruo@yahoo.com \
    --cc=nicolasbertolo@gmail.com \
    --cc=npostavs@gmail.com \
    --cc=rudalics@gmx.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).