From: John Soo <jsoo1@asu.edu>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: xorg-configuration questions
Date: Tue, 9 Apr 2019 09:06:41 -0700 [thread overview]
Message-ID: <617B56FE-6762-4894-9BB6-D5376ABCBD43@asu.edu> (raw)
In-Reply-To: <871s2bfcf2.fsf@gnu.org>
Thanks!
I’m all fixed. the extra config is broken but I think that’s an x configuration problem.
- John
> On Apr 9, 2019, at 8:04 AM, Ludovic Courtès <ludo@gnu.org> wrote:
>
> Hi John,
>
> John Soo <jsoo1@asu.edu> skribis:
>
>> I love the idea of having one record for keyboard layout and I just
>> reconfigured my system with the new configuration but my settings won't
>> take. I've had issues with the old `extra-config` options in the past
>> (nothing worked then including the cst-trackball from below). Admittedly, I
>> am quite unfamiliar with xorg configuration of input devices so I can
>> imagine I may be doing something wrong. I've listed what I have so far
>> below. Note that the console keymap works properly. Also the auto-login
>> does not seem to work either. What am I doing wrong?
>>
>> (define ctrl-nocaps (keyboard-layout "us" #:options '("ctrl:nocaps"))
>> ...
>> (define cst-trackball
>> "Section \"InputClass\"
>> Identifier \"CST Trackball\"
>> Driver \"libinput\"
>> MatchVendor \"CST\"
>> MatchProduct \"CST USB UNITRAC\"
>> MatchIsPointer \"on\"
>> Option \"AccelerationNumerator\" \"2.0\" EndSection")
>> ...
>> (modify-services %desktop-services
>> ...
>> ('gdm-service-type c =>
> ^
> This quote shouldn’t be here.
>
> Apart from that, I don’t see anything wrong.
>
> Now that there’s also ‘set-xorg-configuration’ now, which makes Xorg
> configuration slightly less verbose.
>
> HTH,
> Ludo’.
prev parent reply other threads:[~2019-04-09 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-06 21:12 xorg-configuration questions John Soo
2019-04-06 23:04 ` 宋文武
2019-04-09 15:04 ` Ludovic Courtès
2019-04-09 16:06 ` John Soo [this message]
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=617B56FE-6762-4894-9BB6-D5376ABCBD43@asu.edu \
--to=jsoo1@asu.edu \
--cc=help-guix@gnu.org \
--cc=ludo@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).