unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
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, 23 Apr 2020 16:41:03 +0200	[thread overview]
Message-ID: <CAJ3okZ3AE1yHswF9b4XTmuU6h366s-F7RTHh8TbfD=yY6tvDKQ@mail.gmail.com> (raw)
In-Reply-To: <m1h7xah5n8.fsf@fastmail.net>

Hi Konrad,

On Thu, 23 Apr 2020 at 12:13, Konrad Hinsen <konrad.hinsen@fastmail.net> wrote:

> > Why not simply add an option to "guix repl"?
> > For example "--batch", mimicking  "emacs --batch".
> > Or "--script".
>
> Do you have a suggestion for explaining such a command to someone who
> want to run a script bu (1) doesn't know what a REPL is, (2) doesn't
> need to know what a REPL is, (3) would be mystified by the behavior
> resulting from forgetting the –script argument?

If I understand well
     guix run-script file1 file2
is becoming:
    guix repl --script=file1,file2,...
right?

Well, I would say that

--8<---------------cut here---------------start------------->8---
the keyword "repl" stand for Read-Eval-Print-Loop
therefore the command will:
  - read the script file1,
  - eval it,
  - print the results if they are,
  - and finally loop if there is more than one script file.
--8<---------------cut here---------------end--------------->8---

this fills the condition (1) and (2); at least to me. ;-)


I agree that forgetting the argument '--script' could mystified the learner.

But applying the same principles, the command
    guix environment --ad-hoc python -- python
could mystified the learner too, if for example they forgets --ad-hoc
or '-- python'.

Well, this kind of disconcerting "mistakes" is part of the learning
process, IMHO.
Others call that "discoverability". ;-)


> I agree of course that naming is hard, but it is also important.  Git
> should be a sufficient demonstration of what happens when you design
> command-line interfaces by a sequence of cumulative least-effort
> decisions.

I agree.
And I still have in my stack how to propose another CLI naming as we
discussed earlier, e.g.,
    environment, package, etc.
reorganized into
  profile, install, search, etc.


Cheers,
sion

  reply	other threads:[~2020-04-23 14:42 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 [this message]
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='CAJ3okZ3AE1yHswF9b4XTmuU6h366s-F7RTHh8TbfD=yY6tvDKQ@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 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).