From: divoplade <d@divoplade.fr>
To: "Julien Lepiller" <julien@lepiller.eu>,
help-guix@gnu.org, "Wiktor Żelazny" <wz@freeshell.de>
Subject: Re: How do you define a service?
Date: Sat, 17 Oct 2020 23:08:49 +0200 [thread overview]
Message-ID: <a8baf8852d61bcc9bf09e976d4c5e99f9762a834.camel@divoplade.fr> (raw)
In-Reply-To: <8C3A100B-A611-44AA-9D56-EE9605D0BB59@lepiller.eu>
Hello,
Le samedi 17 octobre 2020 à 16:55 -0400, Julien Lepiller a écrit :
> Don't you have one pair of parentheses too much around make-forkexec-
> constructor? I think it may try to evaluate the result as a function
> with no argument if you do that.
Indeed. Thank you!
divoplade
next prev parent reply other threads:[~2020-10-17 21:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-17 15:07 How do you define a service? divoplade
2020-10-17 15:58 ` Wiktor Żelazny
2020-10-17 19:47 ` divoplade
2020-10-17 20:55 ` Julien Lepiller
2020-10-17 21:08 ` divoplade [this message]
2020-10-17 21:42 ` divoplade
2020-10-17 22:18 ` Julien Lepiller
2020-10-18 9:49 ` divoplade
2020-10-18 12:12 ` Julien Lepiller
2020-10-18 14:53 ` divoplade
2020-10-18 15:43 ` divoplade
2020-10-18 16:42 ` Efraim Flashner
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=a8baf8852d61bcc9bf09e976d4c5e99f9762a834.camel@divoplade.fr \
--to=d@divoplade.fr \
--cc=help-guix@gnu.org \
--cc=julien@lepiller.eu \
--cc=wz@freeshell.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.
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).