unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: help-guix@gnu.org,
	"Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de>,
	dikasetyaprayogi@tutamail.com
Subject: Re: help: screen tearing in guix
Date: Fri, 22 Oct 2021 06:54:10 -0400	[thread overview]
Message-ID: <3C1AFAB8-4931-4074-86C0-EC34BDA9C84E@lepiller.eu> (raw)
In-Reply-To: <87pmrxa8j3.fsf@ruhr-uni-bochum.de>

Hi,

I'd be interested in the content of that file. Where does it come from, can you share it? As a bonus, I would be able to use it and help you if I find out how to configure my system to use it :)

Le 22 octobre 2021 02:16:48 GMT-04:00, "Daniel Meißner" <daniel.meissner-i4k@ruhr-uni-bochum.de> a écrit :
>Hi dikasetyaprayogi,
>
>> hello fresh guixsd user here, i had a problem with screen tearing.
>>
>> usually in my other parabola gnu linux machine i just make intel anti
>> tearing conf in /etc/X11/xorg.conf.d/20-intel.conf and the problem
>> gone.
>>
>> when i do this in guix looks there is no effect, any way how to
>> integrate this to guixsd? thanks.
>
>The system configuration of Guix works a little differently from
>manipulating the config files directly.  Instead, the whole system
>configuration is done inside of an operating-system record in a Scheme
>file (see [1] for more info).  You can add your Xorg configuration to
>the xorg-configuration record field of your display manager (see [2])
>and then run `guix system reconfigure /path/to/your/config.scm'.  If you
>have installed Guix via its graphical installer you should find your
>system configuration at `/etc/config.scm'.
>
>Best
>Daniel
>
>1: https://guix.gnu.org/de/manual/devel/en/html_node/Using-the-Configuration-System.html
>2: https://guix.gnu.org/de/manual/devel/en/html_node/X-Window.html#X-Window
>

  reply	other threads:[~2021-10-22 10:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-22  2:31 help: screen tearing in guix dikasetyaprayogi--- via
2021-10-22  6:16 ` Daniel Meißner
2021-10-22 10:54   ` Julien Lepiller [this message]
2021-10-22 14:33     ` dikasetyaprayogi--- via
2021-10-23 20:50       ` Ekaitz Zarraga
2021-10-23 22:18         ` dikasetyaprayogi--- via
2021-10-24 10:48           ` Ekaitz Zarraga
2021-10-24 10:54             ` Pascal Lorenz
2021-10-24 11:00               ` Ekaitz Zarraga
2021-10-24 18:55                 ` André A. Gomes
2021-10-24 18:47         ` André A. Gomes
2021-10-27 10:03           ` Ekaitz Zarraga

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=3C1AFAB8-4931-4074-86C0-EC34BDA9C84E@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=daniel.meissner-i4k@ruhr-uni-bochum.de \
    --cc=dikasetyaprayogi@tutamail.com \
    --cc=help-guix@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.
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).