From: Rostislav Svoboda <rostislav.svoboda@gmail.com>
To: Ian Eure <ian@retrospec.tv>, guix-devel <guix-devel@gnu.org>
Subject: Re: Guix CLI, thoughts and suggestions
Date: Thu, 18 Jan 2024 14:51:15 +0100 [thread overview]
Message-ID: <CAEtmmey5MaZqGwJw71RYxYzB9vpWdRz2DV-N5VX+uv3FoVrFnA@mail.gmail.com> (raw)
In-Reply-To: <Zad_7mdjzK72aipf@3900XT>
I find the discrepancy regarding two dashes '--' is annoying:
$ guix package --list-generations=1d
...
$ guix describe --list-generations=1d
guix system: error: list-generations=1d: unrecognized option
$ guix describe list-generations=1d
...
And more importantly, I'd be happy if the CLI and REPL syntax were
united, so that there's minimal difference between a shell command
call and a Guile function call. E.g. following would do the same:
$ guix :show emacs
scheme@(guix-user)> (guix :show emacs)
This would greatly facilitate the shell-to-Guile script conversion.
(This way, for comp-sci newcomers, it's much easier to see what a
(bash) shell, with its quirky DSL, really is - not an interface making
computers easier to use, but a barrier obstructing you from properly
using computers as programmable stateful machines. See
https://www.gnu.org/software/guile/manual/html_node/Prompts.html )
Unfortunately, the '#' indicates a comment-start in shells and, as
AFAICS in the source code, we prefer the #:keyword syntax over
:keyword. (Here, in the first step, on an experimental branch, we
could try to add (read-set! keywords 'prefix) everywhere, just to see
what breaks ;-)
Cheers Bost
prev parent reply other threads:[~2024-01-18 18:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-15 19:24 Guix CLI, thoughts and suggestions Ian Eure
2024-01-15 21:01 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2024-01-15 22:08 ` Carlo Zancanaro
2024-01-20 22:50 ` Ian Eure
2024-01-22 0:21 ` Carlo Zancanaro
2024-02-04 12:21 ` Rostislav Svoboda
2024-01-17 7:21 ` Efraim Flashner
2024-01-18 13:51 ` Rostislav Svoboda [this message]
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=CAEtmmey5MaZqGwJw71RYxYzB9vpWdRz2DV-N5VX+uv3FoVrFnA@mail.gmail.com \
--to=rostislav.svoboda@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ian@retrospec.tv \
/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.