unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ng0 <ngillmann@runbox.com>
To: swedebugia@riseup.net, guix-devel <guix-devel@gnu.org>
Subject: Re: Colors and progress indicators on buildprocesses
Date: Wed, 28 Sep 2016 09:57:16 +0000	[thread overview]
Message-ID: <87y42c4a9v.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87d5b525ac5a11f0152902458a35120a@riseup.net>

swedebugia@riseup.net writes:

> Hi
>
> I recently installed Parabola and have played around a bit with 
> compiling AUR-packages to be able to run the programs I want - packaged 
> or not.
>
> Having build a lot on guixsd a while ago I noticed some differences in 
> the cli-overview that I would like to present.
>
> Colorfication and arrows (=>) are used to clearly distinguish 
> pacaur/pacman-commands from the buildprocess output.
>
> A nice thing I saw on some builds (build of qt during build of 
> telegram-desktop) was a per build process percentage indicator located 
> in the beginning of each line of build output like this:
> [ 0% ] lorem ipsum....
> [ 10% ] lorem ipsum....
>
> In addition to these two above I have an idea as well:
> Use the terminal-title wisely to show the progress of the whole 
> transaction and the current running build (e.g.: "Download complete. 
> Buildprogress 4/5: building qt"
>
> What do you think?
>
>

The problem with colors is that the use of colors in build logs creates
very difficult to read logs if you don't filter them. I think this is
one of the reasons why we don't have colors.
I am not against it, I just think it will make helping people a little
harder when they provide such logs. On the other hand, if we manage to
filter the colors out in the build logs somehow, this is of no concern
to us.
-- 
              ng0

  reply	other threads:[~2016-09-28  9:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-28  9:38 Colors and progress indicators on buildprocesses swedebugia
2016-09-28  9:57 ` ng0 [this message]
2016-09-28 13:55   ` swedebugia
2016-09-28 14:05   ` John Darrington
2016-09-28 14:39     ` Troy Sankey
2016-09-30 20:41 ` Ludovic Courtès

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=87y42c4a9v.fsf@we.make.ritual.n0.is \
    --to=ngillmann@runbox.com \
    --cc=guix-devel@gnu.org \
    --cc=swedebugia@riseup.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).