From: Paul Jewell via <help-guix@gnu.org>
To: help-guix@gnu.org
Subject: Re: home-files-service-type - naming restrictions?
Date: Mon, 26 Dec 2022 16:48:08 +0000 [thread overview]
Message-ID: <3aa58fd3-0bfb-955f-3607-ea7e6bb5cb90@teulu.org> (raw)
In-Reply-To: <20c3fa76-7ea6-6565-f569-90d48b602856@teulu.org>
On 26/12/2022 14:53, Paul Jewell via wrote:
> Good afternoon,
>
> I have a home configuration which has worked without issue for some
> time, but now I wanted to add the configuration files for urxvt:
>
> (home-environment
> (packages ...)
> (services
> (list
> ...
> (simple-service 'urxvt-config
> home-files-service-type
> (list `(".Xresources"
> ,(local-file
> "/home/paul/dotfiles/home/file/.Xresources"))
> `(".config/urxvt"
> ,(local-file
> "/home/paul/dotfiles/home/files/.config/urxvt")))))
>
> I am getting the error:
>
> guix home: error: invalid name: `.Xresources'
>
> This leads me to three questions:
> 1. Is there a constraint on file naming with home-files-service-type?
> 2. If so, is there another mechanism I am supposed to use to create
> .Xresources?
> 3. So I can find my way through this type of problem in the future, is
> there some way I can see the source code to home-files-service-type
> apart from digging? For a package, I know I can use guix edit
> <pkg-name> to see the definition, but I can't see how to do this for
> home-files-service-type.
>
> Thanks!
>
Turns out the problem is the leading fullstop in the .Xresources part of
the filename string. If I rename the file with the leading point, and
modify the file name string accordingly, it all works.
Is this a bug? I would expect any valid filename to be accepted in this
context.
My next problem - xrdb isn't executed when I log into the session -
guess I need to put this in one of the start up scripts!
Best regards,
Paul
prev parent reply other threads:[~2022-12-26 16:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-26 14:53 home-files-service-type - naming restrictions? Paul Jewell via
2022-12-26 16:48 ` Paul Jewell via [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
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=3aa58fd3-0bfb-955f-3607-ea7e6bb5cb90@teulu.org \
--to=help-guix@gnu.org \
--cc=paul@teulu.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).