From: Carlo Zancanaro <carlo@zancanaro.id.au>
To: Joshua Branson <jbranso@dismail.de>
Cc: guix-devel@gnu.org
Subject: Re: awesome window manager configuration
Date: Sat, 05 Jan 2019 09:44:42 +1100 [thread overview]
Message-ID: <878t0059kn.fsf@zancanaro.id.au> (raw)
In-Reply-To: <87wonkvcie.fsf@dismail.de>
Hi Joshua!
On Fri, Jan 04 2019, Joshua Branson wrote:
> I recently started using the awesome window manager, and I'm
> curious if I can help edit the manual a bit. The current manual
> does not mention that to configure the awesome window manager,
> one must copy the configuration from
> /gnu/store/xmmqxby6bm...-awesome-4.2/etc/xdg/awesome/rc.lua to
> "~/.config/awesome/".
>
> My question is for now, can I add that information to the
> manual?
It would be great if you could add that to the manual! The usual
advice for awesome is to copy it from /etc/xdg/awesome/rc.lua, so
it's worth documenting that it's different on Guix. It might be
worth saying to copy it from the relevant profile, rather than the
specific store directory. The profile would usually be either
~/.guix-profile/etc/xdg/awesome/rc.lua (if it's installed as a
user package), or
/run/current-system/profile/etc/xdg/awesome/rc.lua (if it's
installed as a system package).
> My second question is what is the long term plan for integrating
> window managers with guixSD? Should be turn all window manager
> packages into services? ...
I don't think we need to do this. As long as they work (and are
picked up by DMs) when installed as a package, I think that's
sufficient. I actually don't even have Awesome installed as a
system package - I install it as a user package and configure my
DE (xfce, which is installed as a system package) to start Awesome
from my user profile.
Carlo
prev parent reply other threads:[~2019-01-04 22:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 12:22 awesome window manager configuration Joshua Branson
2019-01-04 22:44 ` Carlo Zancanaro [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878t0059kn.fsf@zancanaro.id.au \
--to=carlo@zancanaro.id.au \
--cc=guix-devel@gnu.org \
--cc=jbranso@dismail.de \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.