From: zimoun <zimon.toutoune@gmail.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: objections to short syntax for code snippets?
Date: Wed, 5 Feb 2020 15:40:54 +0100 [thread overview]
Message-ID: <CAJ3okZ01=3w7Jj_1_A_T2DAy3fgzuVpXBDYK4hdySwbZcCbp=A@mail.gmail.com> (raw)
In-Reply-To: <871rrasdsl.fsf@elephly.net>
Hi Ricardo,
On Tue, 4 Feb 2020 at 14:06, Ricardo Wurmus <rekado@elephly.net> wrote:
> --8<---------------cut here---------------start------------->8---
> process run-sh
> inputs
> . "a"
> . mine: "b"
> . "c"
> . yours: "d"
> # {
> echo "This is mine: {{inputs:mine}}, and this is yours: {{inputs:yours}}."
> }
> --8<---------------cut here---------------end--------------->8---
This is cool!
Aside your question, I am thinking if WISP could be adapted to use
dash '-' instead of dot '.' in the field 'inputs'.
> --8<---------------cut here---------------start------------->8---
> process run-sh
> inputs "hello"
> #{
> function {
> echo "I just want to say something."
> } # this is not a comment
Annoying but I can live with. :-)
> }
> --8<---------------cut here---------------end--------------->8---
> Anyway, do you have any objections to this optional syntax? Any
No objections.
Thank you for all the improvements.
All the best,
simon
next prev parent reply other threads:[~2020-02-05 14:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-04 13:05 objections to short syntax for code snippets? Ricardo Wurmus
2020-02-04 13:31 ` Roel Janssen
2020-02-05 14:40 ` zimoun [this message]
2020-02-05 15:10 ` Ricardo Wurmus
2020-02-05 15:21 ` Pjotr Prins
2020-02-05 15:31 ` zimoun
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://www.guixwl.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAJ3okZ01=3w7Jj_1_A_T2DAy3fgzuVpXBDYK4hdySwbZcCbp=A@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
/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).