From: Mark H Weaver <mhw@netris.org>
To: Roel Janssen <roel@gnu.org>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Xorg tearing fix on Intel HD Graphics 4000
Date: Sun, 25 Jun 2017 07:38:47 -0400 [thread overview]
Message-ID: <87efu8i9fc.fsf@netris.org> (raw)
In-Reply-To: <87k24031ud.fsf@gnu.org> (Roel Janssen's message of "Sun, 25 Jun 2017 10:31:38 +0200")
Roel Janssen <roel@gnu.org> writes:
> Chris Marusich writes:
>
>> Mark H Weaver <mhw@netris.org> writes:
>>
>>> However, your proposed workaround is not a proper fix, and I don't think
>>> we should apply it system-wide in Guix.
>>
>> Can you elaborate on why it is not a proper fix? It isn't obvious to
>> me.
>
> Because it changes Xorg in order to fix a bug in Emacs. A proper fix
> would be in Emacs.
I'm not sure the bug is in Emacs. That was only a guess based on my
limited personal experience. Having read a bit more, I now think it's
more likely to be a problem in the Intel driver, but these are only
guesses in an area where my knowledge is weak.
Mark
next prev parent reply other threads:[~2017-06-25 11:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-21 7:55 Xorg tearing fix on Intel HD Graphics 4000 Roel Janssen
2017-06-21 10:38 ` Ricardo Wurmus
2017-06-21 13:26 ` Roel Janssen
2017-06-21 16:27 ` Kei Kebreau
2017-06-21 17:23 ` Mark H Weaver
2017-06-21 22:21 ` Roel Janssen
2017-06-21 23:23 ` William
2017-06-25 11:59 ` Marius Bakke
2017-06-25 17:13 ` Roel Janssen
2017-06-25 17:39 ` Marius Bakke
2017-06-25 5:47 ` Chris Marusich
2017-06-25 8:31 ` Roel Janssen
2017-06-25 11:38 ` Mark H Weaver [this message]
2017-06-25 11:08 ` Mark H Weaver
2017-08-07 21:48 ` Clément Lassieur
2017-06-25 5:46 ` Chris Marusich
2017-06-25 8:28 ` Roel Janssen
2017-07-20 2:43 ` Chris Marusich
2017-07-20 10:57 ` Roel Janssen
2017-06-23 18:00 ` Christopher Baines
2017-06-26 8:55 ` Andy Wingo
2017-06-27 17:43 ` Mark H Weaver
2017-06-28 8:24 ` Andy Wingo
2017-06-28 18:14 ` Mark H Weaver
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87efu8i9fc.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=roel@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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).