unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Leo Famulari <leo@famulari.name>
To: gno <gnopap@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: .xinitrc ignored
Date: Fri, 19 Aug 2016 17:57:16 -0400	[thread overview]
Message-ID: <20160819215716.czxoo6b6fcswxvty@jasmine> (raw)
In-Reply-To: <20160819213320.32905286@gmail.com>

On Fri, Aug 19, 2016 at 09:33:20PM +0200, gno wrote:
> Hello guys !
> 
> First off, guix is great, even if it takes quite some time to get used
> to :)
> 
> I made it work in no time and am now running guixsd (lightweight
> desktop setup with awesome). I'd like to keep at it but I do need to
> solve 2 problems first. I was asking around in #guix and was referred
> to this email add.
> 
> Is there any way to make it respect .xinitrc, preferrably when slim
> starts ? I use a diy keyboard with a custom xmodmap that needs to be
> loaded. I tried all kinds of things with ~ and
> root; .xinitrc, .xserverrc, .xsession (crashed w/o logs).

I'm not sure — someone else will have to answer this.

> Also, unfortunately awesome-wm is quite dated. I'd like to update it so
> that it is compatible with my config. There have been quite a few API
> changes. Is it feasible to try and package a newer version myself or
> did you not do it already because of missing dependencies or other
> complications ?

Please, feel free to try updating it to the latest upstream release :) I
haven't heard of any reasons for it to stay at the current version.

  reply	other threads:[~2016-08-19 21:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-19 19:33 .xinitrc ignored gno
2016-08-19 21:57 ` Leo Famulari [this message]
2016-08-20  2:36 ` 宋文武
2016-08-20 18:05   ` gno
2016-08-20 19:58 ` ng0
2016-08-20 23:34   ` .xinitrc ignored; awesome-wm gno
2016-08-21 10:26 ` .xinitrc ignored Andreas Enge

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=20160819215716.czxoo6b6fcswxvty@jasmine \
    --to=leo@famulari.name \
    --cc=gnopap@gmail.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).