all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Matt Huszagh <huszaghmatt@gmail.com>
Cc: 37335@debbugs.gnu.org, stefan@marxist.se
Subject: bug#37335: 27.0.50; screen glitches even with double buffering inhibited
Date: Sat, 25 Jan 2020 09:33:13 +0200	[thread overview]
Message-ID: <83eevoq9c6.fsf@gnu.org> (raw)
In-Reply-To: <87eevoindi.fsf@gmail.com> (message from Matt Huszagh on Fri, 24 Jan 2020 12:57:13 -0800)

> From: Matt Huszagh <huszaghmatt@gmail.com>
> Cc: 37335@debbugs.gnu.org
> Cc: 
> Date: Fri, 24 Jan 2020 12:57:13 -0800
> 
> Unfortunately the fixes didn't work for me. Additionally, I've recently
> changed from a computer using a Nvidia GPU to one using an AMD GPU and
> I'm seeing the same issue. I guess it could be an issue with the
> xserver? I'd be surprised though, because I have a relatively new
> version of X.
> 
> That said, I disabled cursors in non-selected windows,
> 
> (setq-default cursor-in-non-selected-windows nil)
> 
> which makes the issue much less annoying, so I'm not too concerned with
> it anymore.

It is still something that's related to your local configuration,
because the few other people who reported such display problems
eventually found them to be related to the software installed on their
machines, not to Emacs.

Also, can you see these problems in "emacs -Q"?





  reply	other threads:[~2020-01-25  7:33 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-07 20:44 bug#37335: 27.0.50; screen glitches even with double buffering inhibited Matt Huszagh
2019-09-08  2:33 ` Eli Zaretskii
2019-09-08  3:01   ` Matt Huszagh
2019-09-08  4:02     ` Eli Zaretskii
2020-01-24 18:18       ` Stefan Kangas
2020-01-24 20:57         ` Matt Huszagh
2020-01-25  7:33           ` Eli Zaretskii [this message]
2020-04-24  9:57             ` Stefan Kangas

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=83eevoq9c6.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=37335@debbugs.gnu.org \
    --cc=huszaghmatt@gmail.com \
    --cc=stefan@marxist.se \
    /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.