unofficial mirror of gwl-devel@gnu.org
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: zimoun <zimon.toutoune@gmail.com>
Cc: gwl-devel@gnu.org
Subject: Re: variable interpolation in code snippets
Date: Tue, 26 Feb 2019 09:12:25 +0100	[thread overview]
Message-ID: <87mumj0xzq.fsf@elephly.net> (raw)
In-Reply-To: <CAJ3okZ0_+pjQ6bt4tpAMpgr2cHf5j-am80UemWKo31MFcPUo-w@mail.gmail.com>


zimoun <zimon.toutoune@gmail.com> writes:

> A quick question. The `data-inputs` is a list, so `print
> "{{data-inputs}}` should return:
>      "sample.bam" "hg38.fa" "abc"
> Right?
>
> How to refer to "hg38.fa" only?
>
>    print "{{second data-inputs}}"

That’s not possible, unfortunately.  Currently, the list is merely
converted to a string, so (list "sample.bam" "hg38.fa" "abc") becomes
the string “sample.bam hg38.fa abc”.  For singleton lists that’s exactly
what you want, but it’s not great for longer lists.

I thought about adding support for selectors, but I don’t know if I
should.  Maybe it would be better to allow for named inputs instead,
which would result in process-local bindings.

This would probably require changes to the records macro that we took
from Guix.  I’d prefer that over implementing a small language in a
reader macro.

--
Ricardo

  reply	other threads:[~2019-02-26  8:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 14:50 variable interpolation in code snippets Ricardo Wurmus
2019-02-25 23:00 ` zimoun
2019-02-26  8:12   ` Ricardo Wurmus [this message]
2019-02-26 17:35     ` zimoun
2019-02-26 19:04       ` Ricardo Wurmus
2019-02-26 19:29         ` zimoun
2019-05-29 13:27           ` Ricardo Wurmus
2019-06-03 14:54             ` zimoun
2019-06-03 16:04               ` Ricardo Wurmus
2019-06-03 18:19                 ` Roel Janssen
2019-06-07 14:59                 ` Ricardo Wurmus

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=87mumj0xzq.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=gwl-devel@gnu.org \
    --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).