From mboxrd@z Thu Jan 1 00:00:00 1970 From: Leo Famulari Subject: Re: .xinitrc ignored Date: Fri, 19 Aug 2016 17:57:16 -0400 Message-ID: <20160819215716.czxoo6b6fcswxvty@jasmine> References: <20160819213320.32905286@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48158) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1barn8-0005Ym-PK for help-guix@gnu.org; Fri, 19 Aug 2016 17:57:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1barn4-0000Ku-Iw for help-guix@gnu.org; Fri, 19 Aug 2016 17:57:29 -0400 Received: from out2-smtp.messagingengine.com ([66.111.4.26]:35939) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1barn3-0000Kj-CA for help-guix@gnu.org; Fri, 19 Aug 2016 17:57:26 -0400 Content-Disposition: inline In-Reply-To: <20160819213320.32905286@gmail.com> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-guix-bounces+gcggh-help-guix=m.gmane.org@gnu.org Sender: "Help-Guix" To: gno Cc: help-guix@gnu.org 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.