unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: hiding “guix system” messages
Date: Wed, 22 Aug 2018 16:23:40 +0200	[thread overview]
Message-ID: <87zhxefpjn.fsf@gnu.org> (raw)
In-Reply-To: <87va83sfuz.fsf@elephly.net> (Ricardo Wurmus's message of "Tue, 21 Aug 2018 21:02:12 +0200")

Hello!

Ricardo Wurmus <rekado@elephly.net> skribis:

> when installing / building / reconfiguring a system, Guix spawns a few
> tools that produce output that might be confusing or misleading.  One
> example is the output of the GRUB installation, which says things like
> “Installation finished. No error reported.” or that it’s installing
> something for a 386 system.
>
> I think we should hide (redirect to a log file) or at least prefix
> messages that are produced by tools that Guix spawns.  We could then
> deliberately print messages that indicate the “phases” of installing the
> system, such as “Installing GRUB…”, “Creating user accounts…”, etc.

Prefixing sounds like a good idea; hiding might end up hiding too much,
so I’m more wary about that.

If we do prefixing, probably we just need a variant of ‘invoke’ that
runs the program in a pipe, reads its output, and prints the prefixed
lines.

Thoughts?

Ludo’.

      parent reply	other threads:[~2018-08-22 14:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-21 19:02 hiding “guix system” messages Ricardo Wurmus
2018-08-22  6:44 ` Hartmut Goebel
2018-08-22 14:23 ` Ludovic Courtès [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

  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=87zhxefpjn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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).