From: Simon Tournier <zimon.toutoune@gmail.com>
To: Maxim Cournoyer <maxim.cournoyer@gmail.com>, jgart <jgart@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: -v, --verbosity=LEVEL use the given verbosity LEVEL
Date: Wed, 11 Oct 2023 16:09:40 +0200 [thread overview]
Message-ID: <87bkd5tfmj.fsf@gmail.com> (raw)
In-Reply-To: <87bkdo29gh.fsf@gmail.com>
Hi,
On Tue, 26 Sep 2023 at 12:19, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:
>> Where should the user of the Guix command-line interface be expected
>> to read about the verbosity LEVEL argument that they can pass to
>> `--verbosity` and that is also valid?
To answer a question elsewhere in this threads, I think these levels
come from Nix and daemon side.
> See info '(guix) Invoking guix build':
>
> --8<---------------cut here---------------start------------->8---
> ‘-v LEVEL’
> ‘--verbosity=LEVEL’
> Use the given verbosity LEVEL, an integer. Choosing 0 means that
> no output is produced, 1 is for quiet output; 2 is similar to 1 but
> it additionally displays download URLs; 3 shows all the build log
> output on standard error.
> --8<---------------cut here---------------end--------------->8---
Maybe, we could add an option as ’--list-verbosity’ which would display
that information.
Well, the main issue, IMHO, is that the option ’--verbosity’ is not
shared across various command-line scripts, but implemented script per
script, IIRC.
Cheers,
simon
next prev parent reply other threads:[~2023-10-11 14:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 18:08 -v, --verbosity=LEVEL use the given verbosity LEVEL jgart
2023-09-26 16:19 ` Maxim Cournoyer
2023-10-11 14:09 ` Simon Tournier [this message]
2023-10-11 15:11 ` Maxim Cournoyer
2023-10-11 15:36 ` Simon Tournier
2023-09-26 16:33 ` jgart
2023-09-26 16:42 ` Maxim Cournoyer
2023-09-26 16:56 ` jgart
2023-09-26 20:39 ` jgart
2023-10-01 22:16 ` Maxim Cournoyer
2023-10-02 2:21 ` jgart
2023-10-04 1:02 ` Maxim Cournoyer
2023-10-05 15:03 ` jgart
2023-10-12 13:34 ` Simon Tournier
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=87bkd5tfmj.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
--cc=maxim.cournoyer@gmail.com \
/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.
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).