unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
To: "Jakub Kądziołka" <kuba@kadziolka.net>
Cc: help-guix@gnu.org
Subject: Re: How to specify custom remappings with keyboard-layout?
Date: Tue, 7 Apr 2020 03:50:38 +0200	[thread overview]
Message-ID: <20200407015038.adayciaclc4l7t74@pelzflorian.localdomain> (raw)
In-Reply-To: <20200406110502.unkhcuhx6m6mzta6@gravity>

[-- Attachment #1: Type: text/plain, Size: 1365 bytes --]

On Mon, Apr 06, 2020 at 01:05:02PM +0200, Jakub Kądziołka wrote:
> On Mon, Apr 06, 2020 at 03:22:29AM +0200, pelzflorian (Florian Pelz) wrote:
> > On Mon, Apr 06, 2020 at 03:05:24AM +0200, pelzflorian (Florian Pelz) wrote:
> > > You could probably use an .xinitrc file like Arch or you could patch
> > > xorg-server to use your xkbcomp map by default.
> > 
> > That is, instead of patching xorg-server, you would patch
> > xkeyboard-config’s xkb/symbols.  I have not tried.  Maybe better use
> > .xinitrc?
> 
> That's not a terrible idea, though I'd rather have it apply even before
> I'm logged in. (I previously mentioned GDM, though I now realize that I
> actually use SLiM.) Is there an equivalent file I could use to run a
> command when the login manager is starting?
> 
> Regards,
> Jakub Kądziołka

I thought it was sufficient to add the files both to your home
directory and to root’s because SLIM is run as root.

But: Actually it seems the gnu/services/xorg.scm is defined in a way
that does not run ~/.xinitrc.  Sorry for not being helpful.  I tried
but was *not* able to modify gnu/services/xorg.scm to run xkbcomp on a
custom ~/.Xkeymap file, although manual execution after the session
started works fine.  Changing the xinitrc does not appear to work.

The attached changes are insufficient.

Regards,
Florian

[-- Attachment #2: xkeymap.patch --]
[-- Type: text/plain, Size: 839 bytes --]

diff --git a/gnu/services/xorg.scm b/gnu/services/xorg.scm
index d0196a299e..5ddf41dafd 100644
--- a/gnu/services/xorg.scm
+++ b/gnu/services/xorg.scm
@@ -403,8 +403,13 @@ desktop session from the system or user profile will be used."
 
             ;; The '--login' option is supported at least by Bash and zsh.
             (execl shell shell "--login" "-c"
-                   (string-join (cons command args)))))
-
+                   (string-join (cons*
+                                 #$(file-append xkbcomp "/bin/xkbcomp")
+                                 (string-append (getenv "HOME") "/.Xkeymap")
+                                 (getenv "DISPLAY")
+                                 ";"
+                                 command args)))))
+        
         (define system-profile
           "/run/current-system/profile")
 

  reply	other threads:[~2020-04-07  1:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-05 22:18 How to specify custom remappings with keyboard-layout? Jakub Kądziołka
2020-04-06  1:05 ` pelzflorian (Florian Pelz)
2020-04-06  1:22   ` pelzflorian (Florian Pelz)
2020-04-06 11:05     ` Jakub Kądziołka
2020-04-07  1:50       ` pelzflorian (Florian Pelz) [this message]
2020-04-07  9:36     ` pelzflorian (Florian Pelz)

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=20200407015038.adayciaclc4l7t74@pelzflorian.localdomain \
    --to=pelzflorian@pelzflorian.de \
    --cc=help-guix@gnu.org \
    --cc=kuba@kadziolka.net \
    /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).