From: zimoun <zimon.toutoune@gmail.com>
To: Bengt Richter <bokr@bokr.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: hide more output
Date: Thu, 7 May 2020 01:25:54 +0200 [thread overview]
Message-ID: <CAJ3okZ1MZra=fKBnurOgyhvxDAc8-93V0qCq_G9gcEFixFZpbw@mail.gmail.com> (raw)
In-Reply-To: <20200506200025.GA4869@LionPure>
On Wed, 6 May 2020 at 22:01, Bengt Richter <bokr@bokr.com> wrote:
> Just so I don't have to re-run something very timeconsuming to see the verbose version.
In this case, you can always run the command using the verbose option.
It is the same with all the CLI I know, one cannot have the milk and
the butter for the same price. ;-)
> IOW, if there isn't one, I think there ought to be a default detailed log
> produced (while teeing through optional verbosity/brevity filters or the user's grep.
This is an interesting idea. Something under '/var/log/guix/per-user'.
But this is a piece of work -- from what I understand -- and I am not
sure if it will provide really more useful information. A lot of
information is already tracked, e.g., "guix pull -l", "guix package
-l", "guix build -n" and "guix build -d", "guix graph", "guix size".
What seems missing is the origin of the packages (substitute by which
server or built locally). Well, I am not convinced by the usefulness
of a detailed log mechanism. I do not know...
All the best,
simon
next prev parent reply other threads:[~2020-05-06 23:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-06 13:38 hide more output Ricardo Wurmus
2020-05-06 14:08 ` Jan Nieuwenhuizen
2020-05-06 14:26 ` zimoun
2020-05-06 14:25 ` Ludovic Courtès
2020-05-06 14:28 ` zimoun
2020-05-06 20:00 ` Bengt Richter
2020-05-06 23:25 ` zimoun [this message]
2020-05-06 14:55 ` Pierre Neidhardt
2020-05-17 22:02 ` Ludovic Courtès
2020-05-18 8:47 ` Pierre Neidhardt
2020-05-18 9:10 ` Jelle Licht
2020-05-18 13:10 ` Katherine Cox-Buday
2020-05-18 13:13 ` Nicolò Balzarotti
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='CAJ3okZ1MZra=fKBnurOgyhvxDAc8-93V0qCq_G9gcEFixFZpbw@mail.gmail.com' \
--to=zimon.toutoune@gmail.com \
--cc=bokr@bokr.com \
--cc=guix-devel@gnu.org \
/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.