On Wed, Jul 16, 2025 at 12:41:07PM +0100, Daniel Hatton wrote: > On 16/07/2025 10:08, Steve George wrote: > > > In this case I would use Guix Home to copy a ~/.Xresources file in and not > > worry about configuring > X if it works for you. > > Thanks. That means I have to write something in a *.scm file to import my > .Xresources, right? The syntax of *.scm files looks a lot harder and more > unforgiving than writing the .Xresources, so I think I'll leave that for a > day when I'm feeling stronger. (...)
No, it means you can *continue* to use the format / files you understand well -
in this case ~/.Xresources - so there's less migration for you to do.
Let me restate. Guix is 'just' Linux underneath - so X Windows is still there
and if you copied your personal ~.Xresources file into your guix machine's home
directory (and restarted X) then it will work as you expect. So I was trying to
convey that you can continue to use the configuration files you're used to.
Rather than manually doing the 'copy my configuration files to my machine'
part, I suggested that you automate that using Guix Home. But, it's optional
and you could do it by any method you like.
When you create a Guix System it puts an initial Guix Home configuration in
your home directory for you. The service/modules concept is the same and
there's a service called `home-files-service` which can copy files. It would
look something like this:
(service home-files-service-type
`((".mutt/muttrc" ,(local-file "files/muttrc"))
This creates a symlink ``$HOME/.mutt/muttrc`` which points to the file which
has been put into the Guix store. The only think to be aware of his that when
ou use ``localfile`` it looks for the file relative to ``home-environment``
configuration file.
Hope that I did a better job explaining this time!
Steve / Futurile
signature.asc
Description: PGP signature
