all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Phil <phil@beadling.co.uk>
To: help-guix@gnu.org
Subject: Disable progress in stdout
Date: Tue, 15 Dec 2020 10:51:55 +0000	[thread overview]
Message-ID: <85eejrxrxw.fsf@beadling.co.uk> (raw)

Hi all,

When running guix from a script the stdout contains various things that
should be disabled unless running interactively - you end up with a log
of stdout containing visual noise.

The -v0 switch doesn't seem to completely quell interactive feedback,
and my aim is not for silence, just for appropriate feedback when not
running manually from the console (i.e. automated via script).

Some other command-line tools have a --progress flag or similar to
disable this - is there an equivalent in Guix?


Examples of unhelpful logging when redirecting to file:

[K100% [#########################################################################]
[K100% [#########################################################################]
[K100% [#########################################################################]

substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...   0.0%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...  12.5%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...  25.0%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...  37.5%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...  50.0%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...  62.5%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...  75.0%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'...  87.5%
substitute: [Kupdating substitutes from 'https://ci.guix.gnu.org'... 100.0%


Thanks,
Phil.



                 reply	other threads:[~2020-12-15 10:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=85eejrxrxw.fsf@beadling.co.uk \
    --to=phil@beadling.co.uk \
    --cc=help-guix@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.