From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "jgart" <jgart@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: -v, --verbosity=LEVEL use the given verbosity LEVEL
Date: Sun, 01 Oct 2023 18:16:22 -0400 [thread overview]
Message-ID: <87jzs656q1.fsf@gmail.com> (raw)
In-Reply-To: <9de75178cdd76d333f78c438a7b8be20@dismail.de> (jgart@dismail.de's message of "Tue, 26 Sep 2023 20:39:38 +0000")
Hi,
"jgart" <jgart@dismail.de> writes:
>> 1 is for quiet output; 2 is similar to 1 but it additionally displays download URLs;
>
>> it additionally displays
>
> I think it is confusing to use the word "additionally" here as there is nothing that we know about the quiet output for the description that let's us then conceptualize what will be added to it.
>
> In other words, level 1 should be described with more detail than "1 is for quiet output".
>
> What should we expect to see in the content of verbosity level 1 in general.
>
> I would have to find the time to conduct some empirical usages with the --verbosity flag to answer that question succinctly and in the general across guix subcommands beyond just describing it as "quiet output".
>
> WDYT, nitpick? maybe/maybenot
I agree it can be improved, but I'd also have to read the code to know
what each level exactly do.
I think it could make things simpler to use nouns for the level, as they
could mean something without having to be explained to verbosely, e.g.:
debug (very verbose)
info (include some extra messages)
warning (warnings and errors -- the default level)
error (errors only)
Basically like what the levels of the 'logging' Python library are
expected to do, which the logging library included with guile-lib is
inspired by.
--
Thanks,
Maxim
next prev parent reply other threads:[~2023-10-01 22:17 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87jzs656q1.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=help-guix@gnu.org \
--cc=jgart@dismail.de \
/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.