From: "Ludovic Courtès" <ludo@gnu.org>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel@gnu.org
Subject: Re: Transformations Shell Syntax
Date: Wed, 16 Aug 2023 16:03:20 +0200 [thread overview]
Message-ID: <87cyzn6q53.fsf@gnu.org> (raw)
In-Reply-To: <5f66af6f-a4c8-451c-fd44-4a3a5c329bc7@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 23 Jul 2023 15:00:16 +0200")
Hi,
Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:
> Am 03.07.23 um 02:01 schrieb jgart:
>> Starting multiple workers:
>>
>> $ herd start microblog-tasks@{1..4}
>> $ herd status microblog-tasks@{1..4}
>
> Please note that this syntax is expanted by the shell! Thus these
> commands are the same as
>
> $ herd start microblog-tasks@1 microblog-tasks@2 microblog-tasks@3
> microblog-tasks@4
> $ herd status microblog-tasks@1 microblog-tasks@2 microblog-tasks@3
> microblog-tasks@4
Ah yes, sorry for not noticing!
The problem with this syntax is that currently ‘start’ procedures can
take an arbitrary number of arguments:
herd start foo x y z
means that the ‘start’ procedure of foo is passed x, y, and z as
arguments. It’s occasionally useful and we do have a few System/Home
services that use it (‘home-pulseaudio-rtp-sink-service-type’,
‘guix-service-type’, ‘documentation-service-type’ in the installer).
So I think we can’t just remove support for that syntax.
Not sure how to improve on that.
Ludo’.
prev parent reply other threads:[~2023-08-16 14:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 6:43 Transformations Shell Syntax jgart
2023-05-23 8:16 ` Efraim Flashner
2023-05-23 9:39 ` Simon Tournier
2023-05-23 13:24 ` jgart
2023-05-23 13:55 ` Andreas Enge
2023-05-23 14:12 ` jgart
2023-05-23 14:22 ` Simon Tournier
2023-05-23 14:28 ` Andreas Enge
2023-05-23 17:20 ` jgart
2023-05-24 3:06 ` Ryan Prior
2023-05-26 15:50 ` Ludovic Courtès
2023-05-27 17:07 ` John Kehayias
2023-07-02 19:54 ` Ludovic Courtès
2023-07-05 20:23 ` John Kehayias
2023-07-03 0:01 ` jgart
2023-07-16 13:14 ` Ludovic Courtès
2023-07-23 13:00 ` Hartmut Goebel
2023-08-16 14:03 ` Ludovic Courtès [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=87cyzn6q53.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).