From: "Ludovic Courtès" <ludo@gnu.org>
To: Dariqq <dariqq@posteo.net>
Cc: Tanguy Le Carrour <tanguy@bioneland.org>,
73383@debbugs.gnu.org,
Maxim Cournoyer <maxim.cournoyer@gmail.com>,
paren@disroot.org, Florian Pelz <pelzflorian@pelzflorian.de>,
Andrew Tropin <andrew@trop.in>
Subject: [bug#73383] [PATCH] home: home-shepherd-configuration: Add silent? field.
Date: Wed, 25 Sep 2024 17:57:10 +0200 [thread overview]
Message-ID: <87y13fsp49.fsf@gnu.org> (raw)
In-Reply-To: <baf4d200c0d625b69b01f63e3013be670461da65.1726835963.git.dariqq@posteo.net> (dariqq@posteo.net's message of "Fri, 20 Sep 2024 12:39:23 +0000")
Hi,
Dariqq <dariqq@posteo.net> skribis:
> * gnu/home/services/shepherd.scm (home-shepherd-configuration): Add silent? field.
> (launch-shepherd-gexp): Conditionally invoke shepherd with --silent.
> * doc/guix.texi (home-shepherd-configuration): Document it.
>
> Change-Id: I1ce7a92c2777ebded39fe293b0bdcbd03562b4fc
[...]
> Related: The daemonize? field is not documented and the accessor is not being
> exported.
We should fix it.
> +@item silent? (default: @code{#f})
> +Whether or not the auto-started Shepherd should output to stdout.
Alternatively: “When true, the @command{shepherd} process does not write
anything to standard output.”
I would go as far as making it #t by default, WDYT?
Thanks,
Ludo’.
next prev parent reply other threads:[~2024-09-25 15:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-20 12:39 [bug#73383] [PATCH] home: home-shepherd-configuration: Add silent? field Dariqq
2024-09-25 15:57 ` Ludovic Courtès [this message]
2024-09-27 14:06 ` Dariqq
2024-10-11 8:39 ` [bug#73383] [PATCH v2 0/2] home-shepherd-configuration: add silent? and document daemonize? Dariqq
2024-10-11 8:39 ` [bug#73383] [PATCH v2 1/2] home: home-shepherd-configuration: Add silent? field Dariqq
2024-10-11 8:39 ` [bug#73383] [PATCH v2 2/2] doc: Document home-shepherd-configuration-daemonize? Dariqq
2024-10-14 11:07 ` bug#73383: [PATCH v2 0/2] home-shepherd-configuration: add silent? and document daemonize? Ludovic Courtès
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=87y13fsp49.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=73383@debbugs.gnu.org \
--cc=andrew@trop.in \
--cc=dariqq@posteo.net \
--cc=maxim.cournoyer@gmail.com \
--cc=paren@disroot.org \
--cc=pelzflorian@pelzflorian.de \
--cc=tanguy@bioneland.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.
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.