From: zimoun <zimon.toutoune@gmail.com>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: "Ludovic Courtès" <ludo@gnu.org>, 40373@debbugs.gnu.org
Subject: [bug#40373] [PATCH] guix: new command "guix run-script"
Date: Thu, 30 Apr 2020 14:42:33 +0200 [thread overview]
Message-ID: <CAJ3okZ3fdyN-v_8eNTb2+F7gNnfPfcYCYutRC2MPxiguh1F+vw@mail.gmail.com> (raw)
In-Reply-To: <m1k11yjn1j.fsf@fastmail.net>
Hi Konrad,
On Wed, 29 Apr 2020 at 18:04, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:
> That's very clever! The weak spot is the P, as script evaluation does
> not print anything. We could make it print the script's return code ;-)
Hum? The usual REPL neither. :-)
Quoting Wikipedia: "print function takes the result yielded by eval"
but from my understanding 'eval' does not always yield a "printable"
result, e.g., "(define foo 42)".
Cheers,
simon
next prev parent reply other threads:[~2020-04-30 12:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-01 14:09 [bug#40373] [PATCH] guix: new command "guix run-script" Konrad Hinsen
2020-04-01 21:00 ` Ludovic Courtès
2020-04-02 7:13 ` Konrad Hinsen
2020-04-02 9:17 ` zimoun
2020-04-02 9:37 ` Konrad Hinsen
2020-04-03 9:17 ` Konrad Hinsen
2020-04-03 9:48 ` Ludovic Courtès
2020-04-03 9:19 ` [bug#40373] [PATCH] guix: new command "guix run" generalizes "guix repl" Konrad Hinsen
2020-04-03 9:51 ` [bug#40373] [PATCH] guix: new command "guix run-script" Ludovic Courtès
2020-04-07 9:10 ` Konrad Hinsen
2020-04-07 10:36 ` Ludovic Courtès
2020-04-17 11:21 ` zimoun
2020-04-23 10:12 ` Konrad Hinsen
2020-04-23 14:41 ` zimoun
2020-04-29 16:04 ` Konrad Hinsen
2020-04-30 12:42 ` zimoun [this message]
2020-05-04 13:54 ` Konrad Hinsen
2020-05-04 17:48 ` zimoun
2020-05-14 9:29 ` Konrad Hinsen
2020-05-14 9:44 ` bug#40373: " zimoun
2020-04-02 9:08 ` [bug#40373] " zimoun
2020-04-02 9:21 ` Konrad Hinsen
2020-04-02 9:25 ` Konrad Hinsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ3fdyN-v_8eNTb2+F7gNnfPfcYCYutRC2MPxiguh1F+vw@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=40373@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.net \
--cc=ludo@gnu.org \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.