From: Efraim Flashner <efraim@flashner.co.il>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 43159@debbugs.gnu.org
Subject: [bug#43159] [PATCH 0/2] Make 'guix help' helpful
Date: Wed, 2 Sep 2020 14:09:53 +0300 [thread overview]
Message-ID: <20200902110953.GB24305@E5400> (raw)
In-Reply-To: <87a6y87bja.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 2207 bytes --]
On Wed, Sep 02, 2020 at 11:50:17AM +0200, Ludovic Courtès wrote:
> Hi,
>
> Efraim Flashner <efraim@flashner.co.il> skribis:
>
> > On Tue, Sep 01, 2020 at 10:35:20PM +0200, Ludovic Courtès wrote:
> >> Hey Guix!
> >>
> >> Here’s another long-overdue change that was brought to my
> >> attention: making ‘guix help’ show a synopsis of each command.
> >> While at it, it also groups them in categories (I more or
> >> less followed the manual, but there’s prolly room for
> >> improvement, like a ‘packaging’ category maybe?):
> >>
> >
> > I dislike the idea that some commands are only for developers and some
> > commands are "too advanced for the common user" (my words, not yours).
>
> Yeah, I’m ambivalent about this as well.
>
> > Before bikeshedding about where the options should be, how about:
> > commands for developers -> commands related to building
>
> Rather, “commands for development“, because that’s really what ‘guix
> environment’ is about, for instance, but saying ‘development’ rather
> than ‘developers’ is probably wise.
>
> > advanced usage -> commands related to verification
>
> Well that only works for ‘challenge’ (which I’d like to put in the hands
> of ‘normal’ users, so I’m not comfortable with the ‘advanced’ label, but
> OTOH, it’s clearly not one of the commands you’d begin with.)
>
> What about archive, copy, download, etc.?
>
It seemed loosely related. If you're running 'guix pull; guix upgrade'
you're not first running 'guix download https://path/to/source.tar.xz'
or copying packages between machines or challenging the reproducibility
of the packages. That's for after you have the packages you want in your
profile or environment.
> > This way they're still "commands for everybody" and they're more
> > descriptive than just "advanced" "expert" and "debug" style headers.
>
> Understood.
>
> Thanks for your feedback!
>
> Ludo’.
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-09-02 11:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-01 20:35 [bug#43159] [PATCH 0/2] Make 'guix help' helpful Ludovic Courtès
2020-09-01 20:41 ` [bug#43159] [PATCH 1/2] scripts: Use 'define-command' and have 'guix help' use that Ludovic Courtès
2020-09-01 20:41 ` [bug#43159] [PATCH 2/2] ui: '--help' output links to <https://guix.gnu.org/help/> Ludovic Courtès
2020-09-02 18:27 ` Maxim Cournoyer
2020-09-02 18:24 ` [bug#43159] [PATCH 1/2] scripts: Use 'define-command' and have 'guix help' use that Maxim Cournoyer
2020-09-03 13:41 ` Ludovic Courtès
2020-09-11 18:58 ` Maxim Cournoyer
2020-09-13 13:03 ` Ludovic Courtès
2020-09-13 23:33 ` Maxim Cournoyer
2020-09-07 12:56 ` [bug#43159] [PATCHES v2] " Ludovic Courtès
2020-09-10 10:34 ` bug#43159: " Ludovic Courtès
2020-09-10 10:55 ` [bug#43159] " Ricardo Wurmus
2020-09-02 8:06 ` [bug#43159] [PATCH 0/2] Make 'guix help' helpful Efraim Flashner
2020-09-02 9:50 ` Ludovic Courtès
2020-09-02 11:09 ` Efraim Flashner [this message]
2020-09-03 16:40 ` zimoun
2020-09-07 12:58 ` Ludovic Courtès
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=20200902110953.GB24305@E5400 \
--to=efraim@flashner.co.il \
--cc=43159@debbugs.gnu.org \
--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).