From: Philipp Stephani <p.stephani2@gmail.com>
To: Katsumi Yamaoka <yamaoka@jpl.org>, 28589-done@debbugs.gnu.org
Subject: bug#28589: 27.0.50; Emacs screen often becomes blank
Date: Tue, 26 Sep 2017 18:31:37 +0000 [thread overview]
Message-ID: <CAArVCkTs_wy4vFDquhwhfRyjjL=++-KELhABz=sswbi4upLeWA@mail.gmail.com> (raw)
In-Reply-To: <b4mh8vqvzmk.fsf@jpl.org>
[-- Attachment #1: Type: text/plain, Size: 1157 bytes --]
Katsumi Yamaoka <yamaoka@jpl.org> schrieb am Di., 26. Sep. 2017 um
06:44 Uhr:
> On Mon, 25 Sep 2017 10:01:30 +0900, Katsumi Yamaoka wrote:
> > Emacs screen often becomes blank or blinks. This didn't happen
> > the last weekend, doesn't happen sometimes but often happens.
> > Changing the window configuration --- scrolling a window, showing
> > a message of two or more lines in the echo area, etc. --- seems
> > to cause it. More funny thing is, when two Emacsen are running,
> > the one of which the frame is not selected becomes blank.
> > Typing any key in the selected blank frame will help, as if
> > (sit-for ∞) is running.
>
> Reverting the change c0af83b[1] solves this problem.
>
> [1]
> Don't attempt to disable double buffering in newer GTK+ versions
> <http://lists.gnu.org/archive/html/emacs-diffs/2017-09/msg00293.html>
>
>
Sigh, I had almost expected this would happen. Reverted with 2fa19cc551.
But now we have another time bomb in the codebase:
the gtk_widget_set_double_buffered function is deprecated and will probably
be removed sometime. This makes the migration to a pure GTK+ build even
more pressing.
[-- Attachment #2: Type: text/html, Size: 1609 bytes --]
next prev parent reply other threads:[~2017-09-26 18:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 1:01 bug#28589: 27.0.50; Emacs screen often becomes blank Katsumi Yamaoka
2017-09-26 4:43 ` Katsumi Yamaoka
2017-09-26 18:31 ` Philipp Stephani [this message]
2017-09-27 8:13 ` martin rudalics
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAArVCkTs_wy4vFDquhwhfRyjjL=++-KELhABz=sswbi4upLeWA@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=28589-done@debbugs.gnu.org \
--cc=yamaoka@jpl.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.