From: Daniel Colascione <dancol@dancol.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25474@debbugs.gnu.org, Ivor Durham <ivor.durham@ivor.cc>
Subject: bug#25474: 26.0.50; Buffer content invisible
Date: Fri, 20 Jan 2017 01:07:29 -0800 [thread overview]
Message-ID: <r025h94u3xri.fsf@dancol.org> (raw)
In-Reply-To: <83d1fi6ufc.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 20 Jan 2017 09:51:19 +0200")
On Fri, Jan 20 2017, Eli Zaretskii wrote:
>> From: "Ivor Durham" <ivor.durham@ivor.cc>
>> Cc: <25474@debbugs.gnu.org>
>> Date: Thu, 19 Jan 2017 09:05:19 -0800
>>
>> Disabling XDBE fixes the problem. Thank you.
>
> Thanks for testing.
>
> Daniel, could you please look into this? If this is something
> specific to this particular X server, and it cannot be fixed/worked
> around in Emacs sources, perhaps we need a run-time option to disable
> double-buffering for a certain display?
I'll take a look. It may be worthwhile to just ditch XDBE and use a
pixmap instead --- that'd complicate the code in Emacs and potentially
(but not necessarily) reduce performance, but it would at least trigger
fewer X server bugs.
In the meantime, you can disable double buffering using the
inhibit-double-buffering frame parameter, e.g.,
(modify-frame-parameters nil '((inhibit-double-buffering . nil)))
next prev parent reply other threads:[~2017-01-20 9:07 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01b001d27170$5730fdb0$0592f910$@durham@ivor.cc>
2017-01-18 15:33 ` bug#25474: 26.0.50; Buffer content invisible Eli Zaretskii
2017-01-18 16:04 ` Ivor Durham
[not found] ` <021001d271a4$9bb87ce0$d32976a0$@durham@ivor.cc>
2017-01-18 16:49 ` Eli Zaretskii
2017-01-18 17:24 ` Ivor Durham
[not found] ` <022401d271af$c4e0ad80$4ea20880$@durham@ivor.cc>
2017-01-18 18:30 ` Eli Zaretskii
2017-01-18 21:27 ` Ivor Durham
[not found] ` <004301d271d1$a802b920$f8082b60$@durham@ivor.cc>
2017-01-19 3:33 ` Eli Zaretskii
2017-01-19 5:03 ` Ivor Durham
[not found] ` <008301d27211$5043d940$f0cb8bc0$@durham@ivor.cc>
2017-01-19 15:51 ` Eli Zaretskii
2017-01-19 15:57 ` Ivor Durham
[not found] ` <00ef01d2726c$cb5cb290$621617b0$@durham@ivor.cc>
2017-01-19 16:17 ` Eli Zaretskii
2017-01-19 17:05 ` Ivor Durham
[not found] ` <00f901d27276$37170a90$a5451fb0$@durham@ivor.cc>
2017-01-20 7:51 ` Eli Zaretskii
2017-01-20 8:02 ` Ivor Durham
2017-01-20 9:07 ` Daniel Colascione [this message]
2017-01-20 10:30 ` Eli Zaretskii
2017-01-20 16:27 ` Ivor Durham
2017-01-20 17:41 ` martin rudalics
2017-01-20 17:42 ` Daniel Colascione
2017-01-20 20:29 ` Ivor Durham
[not found] ` <024c01d2735b$dfee24b0$9fca6e10$@durham@ivor.cc>
2017-01-21 11:59 ` Eli Zaretskii
2017-01-21 13:20 ` martin rudalics
2017-01-21 15:44 ` Eli Zaretskii
2017-01-21 17:04 ` martin rudalics
2017-01-21 16:52 ` Ivor Durham
2017-09-02 12:49 ` Eli Zaretskii
2017-01-18 9:50 Ivor Durham
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=r025h94u3xri.fsf@dancol.org \
--to=dancol@dancol.org \
--cc=25474@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ivor.durham@ivor.cc \
/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.