all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ivor Durham" <ivor.durham@ivor.cc>
To: "'Eli Zaretskii'" <eliz@gnu.org>,
	"'Daniel Colascione'" <dancol@dancol.org>
Cc: 25474@debbugs.gnu.org
Subject: bug#25474: 26.0.50; Buffer content invisible
Date: Fri, 20 Jan 2017 00:02:35 -0800	[thread overview]
Message-ID: <28673.5802110799$1505296834@news.gmane.org> (raw)
In-Reply-To: <83d1fi6ufc.fsf@gnu.org>

My environment in which this problem occurs:

I am using SecureCRT 8.0.3 on a Dell laptop running Windows 10 to connect
via ssh to a Fedora 25 Linux system. The laptop is running VcXsrv 1.15.2.0
as its X server, which is where the blank buffer content is displayed.

-----Original Message-----
From: Eli Zaretskii [mailto:eliz@gnu.org] 
Sent: Thursday, January 19, 2017 11:51 PM
To: Ivor Durham; Daniel Colascione
Cc: 25474@debbugs.gnu.org
Subject: Re: bug#25474: 26.0.50; Buffer content invisible

> 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?






  reply	other threads:[~2017-01-20  8:02 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 [this message]
2017-01-20  9:07                           ` Daniel Colascione
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='28673.5802110799$1505296834@news.gmane.org' \
    --to=ivor.durham@ivor.cc \
    --cc=25474@debbugs.gnu.org \
    --cc=dancol@dancol.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 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.