unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Andreas Enge <andreas@enge.fr>
Cc: bug-guix@gnu.org
Subject: Re: Error messages and progress report
Date: Fri, 11 Jan 2013 15:58:21 +0100	[thread overview]
Message-ID: <877gnj7omq.fsf@gnu.org> (raw)
In-Reply-To: <201301111449.13098.andreas@enge.fr> (Andreas Enge's message of "Fri, 11 Jan 2013 14:49:13 +0100")

Andreas Enge <andreas@enge.fr> skribis:

> Am Donnerstag, 10. Januar 2013 schrieb Ludovic Courtès:
>> I find it useful to have the server name printed (esp. in the case of
>> mirror://, ftpmirror.gnu.org, etc.), so I’ve come up with a solution
>> that abbreviates long URIs like this:
>> I’ll commit it if there are no objections.
>
> This looks good to me.

Great.  Pushed as 28e55604212c01884a77a4f5eb66294c4957c48a.

> I came across another problem: During parallel builds (the norm nowadays), 
> several lines of downloading get mixed, or even the progress numbers are 
> mixed with lines of output from the compiler etc..

Yes.  Unfortunately, the daemon just sends us the build outputs all
mixed up, and there’s no way on the client side to filter that or
anything.

> I do not see what to do about it (except for clearing out a complete
> line, so there is no output trailing after the percentage), and the
> progress indicator can still be used to indicate problems when nothing
> progresses.

I’m not sure how to clear out a complete line.  I don’t want to embed
ncurses just for that.  ;-)

Thanks,
Ludo’.

      reply	other threads:[~2013-01-11 14:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-09 20:01 Error messages and progress report Andreas Enge
2012-12-09 20:50 ` Ludovic Courtès
2012-12-10  9:19   ` Andreas Enge
2012-12-10 13:26     ` Ludovic Courtès
2012-12-10 18:17       ` Andreas Enge
2012-12-10 21:29         ` Ludovic Courtès
2012-12-10 22:12           ` Andreas Enge
2012-12-10 22:59             ` Ludovic Courtès
2012-12-10 23:22               ` Andreas Enge
2012-12-11 12:22                 ` Andreas Enge
2012-12-11 13:20                   ` Nikita Karetnikov
2012-12-11 14:37                   ` Ludovic Courtès
2012-12-11 15:40                     ` Andreas Enge
2012-12-11 21:15                       ` Andreas Enge
2012-12-11 23:16                         ` Ludovic Courtès
2012-12-12  8:55                           ` Andreas Enge
2012-12-13 19:17                             ` Andreas Enge
2012-12-11 23:15                       ` Ludovic Courtès
2012-12-12  8:48                         ` Andreas Enge
2012-12-12 13:14                           ` Ludovic Courtès
2013-01-06 17:49 ` Ludovic Courtès
2013-01-10  9:56   ` Andreas Enge
2013-01-10 10:45     ` Andreas Enge
2013-01-10 21:14       ` Ludovic Courtès
2013-01-11 13:49         ` Andreas Enge
2013-01-11 14:58           ` 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=877gnj7omq.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=andreas@enge.fr \
    --cc=bug-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 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).