From: "Ludovic Courtès" <ludo@gnu.org>
To: Konrad Hinsen <konrad.hinsen@fastmail.net>
Cc: 40373@debbugs.gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: [bug#40373] [PATCH] guix: new command "guix run-script"
Date: Fri, 03 Apr 2020 11:48:11 +0200 [thread overview]
Message-ID: <87r1x4lx2c.fsf@gnu.org> (raw)
In-Reply-To: <m1eet59bcp.fsf@khs-macbook.home> (Konrad Hinsen's message of "Fri, 03 Apr 2020 11:17:58 +0200")
Hi Konrad,
Konrad Hinsen <konrad.hinsen@fastmail.net> skribis:
> Konrad Hinsen <konrad.hinsen@fastmail.net> writes:
>
>> Could we go for "guix guile" and make it option-compatible with plain
>> Guile as much as possible? Just an idea, I am not sure it's a good one!
>> Guile can already be a pain in a shebang line.
>
> After some exploration, that kind of compatibility doesn't seem worth
> the effort.
>
> I will send another patch that implements Simon's proposal:
>
> - New command "guix run" that extends "guix repl" by an optional
> file argument for running a script.
“guix run” was sort of reserved for something else:
https://lists.gnu.org/archive/html/help-guix/2018-01/msg00118.html
The idea is still floating around so perhaps we should keep that name.
> - "guix repl" becomes an alias for "guix run" (and could in the
> long run be declared obsolete).
I’m worried about a possible increase of the deprecation rate. I
understand the rationale, I think it makes sense, but still, I’m not
sure we need to deprecate “guix repl” already.
In fact, since it’s used by inferiors, we must pay extra attention to
keep it as-is as much as possible or we’ll make communication between
old and new Guixes difficult.
Thoughts?
Thanks,
Ludo’.
next prev parent reply other threads:[~2020-04-03 9:49 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 [this message]
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
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r1x4lx2c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=40373@debbugs.gnu.org \
--cc=konrad.hinsen@fastmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).