From: Elias Kueny <elias.kueny@posteo.net>
To: Jelle Licht <jlicht@fsfe.org>
Cc: help-guix@gnu.org
Subject: Re: Running a shell command with home-run-on-change-service-type
Date: Tue, 20 Dec 2022 18:16:17 +0000 [thread overview]
Message-ID: <87ili5hqdt.fsf@posteo.net> (raw)
In-Reply-To: <87zgbiwfh8.fsf@fsfe.org>
On Tue, Dec 20 2022, Jelle Licht wrote:
> ... here you quasi-quote the service extension configuration with
> "`". To make use of a gexp in the expression, we need to unquote the gexp
> expression, so replace "#~" by ",#~".
Thank you, this was the solution!
I expected that replacing the quasi-quote by a normal quote would also do, but apparently no, as it gives the same error as before. And after I changed "#~" by ",#~" as you suggested, "#$(file-append fish "/bin/fish")" started throwing a different error.
But this now works so it's good enough for me:
> (simple-service 'fisher-update-on-change
> home-run-on-change-service-type
> `(("files/.config/fish/fish_plugins"
> ,#~(system* "fish" "-c" "fisher update"))))
prev parent reply other threads:[~2022-12-20 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-19 18:46 Running a shell command with home-run-on-change-service-type Elias Kueny
2022-12-20 10:12 ` Jelle Licht
2022-12-20 18:16 ` Elias Kueny [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=87ili5hqdt.fsf@posteo.net \
--to=elias.kueny@posteo.net \
--cc=help-guix@gnu.org \
--cc=jlicht@fsfe.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).