unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: nljlistbox2@gmail.com (N. Jackson)
To: martin rudalics <rudalics@gmx.at>
Cc: 28652@debbugs.gnu.org
Subject: bug#28652: 26.0.60; Display often "flashes" due to double buffering when switching to Emacs frames
Date: Sat, 30 Sep 2017 15:07:41 -0400	[thread overview]
Message-ID: <87tvzk0zuq.fsf@moondust.localdomain> (raw)
In-Reply-To: <59CF5683.9010807@gmx.at> (martin rudalics's message of "Sat, 30 Sep 2017 10:32:03 +0200")

At 10:32 +0200 on Saturday 2017-09-30, martin rudalics wrote:
>
>> In GNU Emacs 26.0.60 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.22.17)
>>   of 2017-09-24 built on moondust.localdomain
>
> If this happened for a build of master in between commits
>
> c0af83b6ccf2dab9a515dd7f52eb9d4500275ae3
>
> and
>
> 2fa19cc5510cdbf00c54991a9959be984dd99fbe
>
> it would imply that inhibiting double buffering is also needed
> even if it did not cause problems like those from bug#28589. But
> apparently you built from the release branch. So I'm slightly
> confused.
>
> martin

Hi Martin,

Sorry, I don't know if I can help with your confusion.

Yes, I built from the release branch (emacs-26) on 2017-09-24 at
commit d93301242f38d3d9aaa55899c07496f0bdecf391.

The commits you mention were made 2017-08-27 and 2017-09-26
respectively, but neither of them seem to be in the emacs-26
branch.

I am not familiar with bug#28589.

N.






  reply	other threads:[~2017-09-30 19:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-29 18:44 bug#28652: 26.0.60; Display often "flashes" due to double buffering when switching to Emacs frames N. Jackson
2017-09-30  8:32 ` martin rudalics
2017-09-30 19:07   ` N. Jackson [this message]
2017-10-01  8:24     ` martin rudalics
2021-09-03  7:57 ` Lars Ingebrigtsen
2021-09-03 11:52   ` N. Jackson
2021-09-03 12:07     ` Lars Ingebrigtsen

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=87tvzk0zuq.fsf@moondust.localdomain \
    --to=nljlistbox2@gmail.com \
    --cc=28652@debbugs.gnu.org \
    --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).