unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 36594@debbugs.gnu.org
Subject: bug#36594: No hint for missing argument
Date: Thu, 11 Jul 2019 22:40:58 +0200	[thread overview]
Message-ID: <87v9w8pan9.fsf@gnu.org> (raw)
In-Reply-To: <C500F9C2-AEBB-4FE7-A826-A4A75E280031@lepiller.eu> (Julien Lepiller's message of "Thu, 11 Jul 2019 11:49:45 +0200")

Julien Lepiller <julien@lepiller.eu> skribis:

> When you type an option that requires an argument, but don't provide one, you get an error message that says there is a missing argument. There should brobably be a hint on what values are acceptable. For instance, there is no way to know from "guix package -v" or "guix package --help" what values are accepted. In other cases, there is a --list-something option.
>
> Maybe -v is the only case where it would be useful to do something, because you could guess its existence and not use a verbosity level. Maybe fixing the help message to say --verbosity=[0-5] is enough?

Currently it says:

--8<---------------cut here---------------start------------->8---
$ guix build --help | grep -e -verbo
  -v, --verbosity=LEVEL  use the given verbosity LEVEL
--8<---------------cut here---------------end--------------->8---

We could add “an integer between 0 and 2”, but this was left
non-explicit in case we eventually extend it to -7 to +42.

Maybe there’s a limit on what we can do to help users?  :-)

Ludo’.

  reply	other threads:[~2019-07-11 20:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-11  9:49 bug#36594: No hint for missing argument Julien Lepiller
2019-07-11 20:40 ` Ludovic Courtès [this message]
2019-07-11 21:45   ` Julien Lepiller
2019-07-12 20:41     ` 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=87v9w8pan9.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=36594@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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).