From: Kyle Meyer <kyle@kyleam.com>
To: zimoun <zimon.toutoune@gmail.com>, Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org
Subject: Re: Comments on process template syntax
Date: Wed, 05 Feb 2020 15:29:05 +0000 [thread overview]
Message-ID: <87d0at129q.fsf@kyleam.com> (raw)
In-Reply-To: <CAJ3okZ2TpvkGNX3FGjDxTp-fozLboV6fxkDoxA4zfnFZ6UVePw@mail.gmail.com>
zimoun <zimon.toutoune@gmail.com> writes:
> Hi Ricardo,
>
> On Tue, 4 Feb 2020 at 11:12, Ricardo Wurmus <rekado@elephly.net> wrote:
>
> If I understand correctly, you are proposing this sugar:
>
> 1.
>> process list-file-template (with filename)
>
> 2.
>> process list-file-template
>> with filename
>
> 3.
>> process list-file-template : with filename
>
>
> The 1. and 2. appear to me nicer that the 3..
>
> As I said, I am not a fan of colon ':' extra space.
> And it is counterintuitive with plain regular English: the rule is
> "word: space" and not "word space : space".
> (Note that it is not the case in French where the rule is "word
> half-space : space".)
Those are just different ways you can write the same thing in Wisp:
Feeding this
--8<---------------cut here---------------start------------->8---
process list-file-template (with filename)
process list-file-template
with filename
process list-file-template : with filename
--8<---------------cut here---------------end--------------->8---
to wisp2lisp gives:
(process list-file-template (with filename))
(process list-file-template
(with filename))
(process list-file-template (with filename))
next prev parent reply other threads:[~2020-02-05 15:29 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-02 10:20 Comments on process template syntax Ricardo Wurmus
2020-02-02 23:30 ` Kyle Meyer
2020-02-03 8:08 ` Ricardo Wurmus
2020-02-03 14:22 ` Kyle Meyer
2020-02-03 15:23 ` Ricardo Wurmus
2020-02-03 23:16 ` Kyle Meyer
2020-02-04 9:55 ` Ricardo Wurmus
2020-02-05 1:48 ` Kyle Meyer
2020-02-05 15:14 ` zimoun
2020-02-03 8:58 ` Roel Janssen
2020-02-03 12:07 ` Ricardo Wurmus
2020-02-03 12:56 ` Roel Janssen
2020-02-03 14:33 ` Ricardo Wurmus
2020-02-04 10:10 ` Ricardo Wurmus
2020-02-05 2:12 ` Kyle Meyer
2020-02-05 15:21 ` zimoun
2020-02-05 15:29 ` Kyle Meyer [this message]
2020-02-05 15:37 ` zimoun
2020-02-05 16:02 ` Kyle Meyer
2020-02-05 16:23 ` zimoun
2020-02-05 15:07 ` zimoun
2020-02-05 18:04 ` Ricardo Wurmus
2020-02-05 19:14 ` zimoun
2020-02-05 21:32 ` Ricardo Wurmus
2020-02-06 11:59 ` zimoun
2020-02-05 14:56 ` zimoun
2020-02-08 12:34 ` Ricardo Wurmus
2020-02-05 14:50 ` 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=87d0at129q.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=gwl-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=zimon.toutoune@gmail.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.
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).