From: Pjotr Prins <pjotr2020@thebird.nl>
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 09:21:26 -0600 [thread overview]
Message-ID: <20200205152126.uqb4cfmw7rayhgo4@thebird.nl> (raw)
In-Reply-To: <87eev9qdcj.fsf@elephly.net>
It is great to see these examples!
On Wed, Feb 05, 2020 at 04:10:36PM +0100, Ricardo Wurmus wrote:
>
> zimoun <zimon.toutoune@gmail.com> writes:
>
> >> --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---
next prev parent reply other threads:[~2020-02-05 15:29 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
2020-02-05 15:10 ` Ricardo Wurmus
2020-02-05 15:21 ` Pjotr Prins [this message]
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=20200205152126.uqb4cfmw7rayhgo4@thebird.nl \
--to=pjotr2020@thebird.nl \
--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).