unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: swedebugia@riseup.net
Cc: 33673@debbugs.gnu.org
Subject: bug#33673: "guix system --help" does not detail how to use --on-error=strategy
Date: Sun, 09 Dec 2018 00:16:47 +0100	[thread overview]
Message-ID: <87ftv7623k.fsf@gnu.org> (raw)
In-Reply-To: <2a004926090617e0227252136dc35dab@riseup.net> (swedebugia's message of "Sat, 08 Dec 2018 00:30:54 -0800")

Hi,

swedebugia@riseup.net skribis:

> The current output is:
>
> --on-error=STRATEGY    apply STRATEGY when an error occurs while reading
> FILE

FWIW I think it’s reasonable for ‘--help’ to be generally more concise
than the manual.  We could list the possible strategies here, but that
might clutter the output more than is desirable.

> Additionally we now have so many commands in the help pages of guix
> system and guix build that it would be nice to present them in a more
> readable/categorized way.
>
> Would a patches for improvement in these areas be accepted?

Improvements are always welcome of course.  The main criterion would be
to remain consistent with the rest of Guix and with GNU conventions that
we follow.  Maybe it’s best to discuss what you have in mind first?

Thank you,
Ludo’.

  reply	other threads:[~2018-12-08 23:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <87pnuccuk2.fsf@gmail.com>
     [not found] ` <74aa65394c92165fbf4c2f777099eab3@riseup.net>
2018-12-08  8:30   ` bug#33673: "guix system --help" does not detail how to use --on-error=strategy swedebugia
2018-12-08 23:16     ` Ludovic Courtès [this message]
2018-12-11  7:18       ` Efraim Flashner
2018-12-11  7:27         ` swedebugia
2018-12-11 17:10         ` Ludovic Courtès
2018-12-14 18:52           ` bug#33673: PATCH: Fwd: " swedebugia
2018-12-18 10:54             ` 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=87ftv7623k.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=33673@debbugs.gnu.org \
    --cc=swedebugia@riseup.net \
    /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).