all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Wilko Meyer <w@wmeyer.eu>
To: jgart <jgart@dismail.de>
Cc: help-guix@gnu.org
Subject: Re: --debug LEVEL not documented in CLI
Date: Thu, 16 Nov 2023 00:14:53 +0100	[thread overview]
Message-ID: <877cmi4mxk.fsf@wmeyer.eu> (raw)
In-Reply-To: <d92c809819297ac6e6041bdab07a5714@dismail.de>


"jgart" <jgart@dismail.de> writes:
> WDYT

I filed an issue[0] for this and attached a patch with a possible
suggestion on how to improve the --debug as well as --verbosity help
information on CLI as a first draft.

It, with the patch applied, now reads:

--debug=LEVEL      produce debugging output at LEVEL, value must be an integer
between 0 (more terse) and 5 (more verbose)

for debug, and:

-v, --verbosity=LEVEL  use the given verbosity LEVEL, value must be either 0 (no output),
1 (quiet), 2 (quiet + download URLs) or 3 (build log on STDERR)

for verbosity, which should probably suffice to choose an (more)
appropriate debug/verbosity level when debugging from solely reading the
help information.

I tried to keep this as short as possible, a more detailed description
of the debug levels would probably be feasible for the general guix
documentation (also I'm not quite sure how to document them, e.g. what
the exact differences between the five levels are, except that it gets
more verbose, and when to choose which; maybe someone else is more
knowledgable on this?).

[0]: https://issues.guix.gnu.org/67215

-- 
Kind regards,

Wilko Meyer
w@wmeyer.eu


      parent reply	other threads:[~2023-11-15 23:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-15  6:24 --debug LEVEL not documented in CLI jgart
2023-11-15 17:47 ` Wilko Meyer
2023-11-15 23:14 ` Wilko Meyer [this message]

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=877cmi4mxk.fsf@wmeyer.eu \
    --to=w@wmeyer.eu \
    --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.