From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from eggs.gnu.org ([2001:470:142:3::10]:38285)
 by lists.gnu.org with esmtp (Exim 4.90_1)
 (envelope-from <zimon.toutoune@gmail.com>) id 1izM16-00085q-SG
 for gwl-devel@gnu.org; Wed, 05 Feb 2020 09:51:01 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <zimon.toutoune@gmail.com>) id 1izM15-0005TK-PQ
 for gwl-devel@gnu.org; Wed, 05 Feb 2020 09:51:00 -0500
Received: from mail-qk1-x72a.google.com ([2607:f8b0:4864:20::72a]:41784)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
 (Exim 4.71) (envelope-from <zimon.toutoune@gmail.com>)
 id 1izM15-0005PV-Jd
 for gwl-devel@gnu.org; Wed, 05 Feb 2020 09:50:59 -0500
Received: by mail-qk1-x72a.google.com with SMTP id x82so2039379qkb.8
 for <gwl-devel@gnu.org>; Wed, 05 Feb 2020 06:50:59 -0800 (PST)
MIME-Version: 1.0
References: <871rrdthmz.fsf@elephly.net>
In-Reply-To: <871rrdthmz.fsf@elephly.net>
From: zimoun <zimon.toutoune@gmail.com>
Date: Wed, 5 Feb 2020 15:50:48 +0100
Message-ID: <CAJ3okZ3=jv7-jDs5z1_xxVwhgYSFiwa--3cr7JKTRaKVecBHQQ@mail.gmail.com>
Subject: Re: Comments on process template syntax
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
List-Id: <gwl-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/gwl-devel>,
 <mailto:gwl-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/gwl-devel>
List-Post: <mailto:gwl-devel@gnu.org>
List-Help: <mailto:gwl-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/gwl-devel>,
 <mailto:gwl-devel-request@gnu.org?subject=subscribe>
Errors-To: gwl-devel-bounces+kyle=kyleam.com@gnu.org
Sender: "gwl-devel" <gwl-devel-bounces+kyle=kyleam.com@gnu.org>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: gwl-devel@gnu.org

Hi Ricardo,

On Sun, 2 Feb 2020 at 11:20, Ricardo Wurmus <rekado@elephly.net> wrote:

> process: (list-file-template filename)

[...]

> The first line is easy to understand for lispers but it might look weird
> to people who come from other workflow languages or programming
> languages.  This describes a procedure called =E2=80=9Clist-file-template=
=E2=80=9D that
> returns a process parameterized on the argument =E2=80=9Cfilename=E2=80=
=9D.

As you probably know, I am working in a Core Facilities Lab so I am
talking with different profiles of potential users. Based on that it
does not appear to me "weird" because it is "syntax". I mean using
Snakemake, the user has to put <tab>, or semi-colon after 'rule', etc.


> Can we make the common case simpler and easier to understand?  (FWIW, I
> intend to rename the =E2=80=9Cprocess:=E2=80=9D macro to just =E2=80=9Cpr=
ocess=E2=80=9D to remove
> confusing syntactic noise, so anything about the first line may be
> changed.)

I do not have a strong opinion on the subject. :-)


All the best,
simon