unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Troy Sankey <sankeytms@gmail.com>
To: John Darrington <john@darrington.wattle.id.au>,
	ng0 <ngillmann@runbox.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Colors and progress indicators on buildprocesses
Date: Wed, 28 Sep 2016 10:39:53 -0400	[thread overview]
Message-ID: <147507359323.2034.4440394895994902168@what> (raw)
In-Reply-To: <20160928140552.GA30707@jocasta.intra>

[-- Attachment #1: Type: text/plain, Size: 1800 bytes --]

Quoting John Darrington (2016-09-28 10:05:52)
> On Wed, Sep 28, 2016 at 09:57:16AM +0000, ng0 wrote:
>      
>      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. 
> 
> This is true. But the build logs already dump some VT100 escape sequences,
> (for vertical  cursor movement).  And they also have to be filtered, so 
> if we say that colours are not permitted then we are not applying these
> rules consistently.

This is our chance make things right!  Determine if the terminal is
interactive [0] and filter escape codes if yes.

I've used Arch, and the coloring was pleasant, but primarily I enjoyed
the clear (and less buggy) progress bars.  For example:

    $ guix pull
    
    Starting download of /tmp/guix-file.O3WsYp
    From http://git.savannah.gnu.org/cgit/guix.git/snapshot/master.tar.gz...
     ….tar.gz                                   1.7MiB/s 00:06 | 10.5MiB transferred


The "From" line shows what is about to be downloaded, but the progress
par suggests that "….tar.gz" is being downloaded.  There is a lot of
whitespace after that, which is weird.

Also, here's a bug:

    copying and compiling to '/gnu/store/himp5ds1b9m0932dfzxp3gg3vvs7lxd4-guix-latest'...
    loading...       23.1% of 528 filesrandom seed for tests: 1475073161
    loading...       99.8% of 528 files

Something happens during the loading phase, and the string "random seed
for tests: 1475073161" gets printed (also inserting a newline).  The
progress indicator cannot cope, so it starts on a new line.  Also, it
stops at 99.8% which is confusing.

These non-color issues are more important to resolve, IMO.

Troy

[0] http://www.tldp.org/LDP/abs/html/intandnonint.html

[-- Attachment #2: signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAABCAAGBQJX69Y2AAoJEIRGmXXw0dCU9Y0P/jELb24uNt7NVSuhQcqVtV77
iybHmudYoTgXwQUSyoaLqJMRe4UDP3Y8nf34LuDMAqVyAhtr4a8CEaUUlUnsnnTi
FBghD/W0XsIGZzJPI2IpTtyakO6HC7R5WCzGWX9KyzpamLb7+A9lRHbtQ7c8gMC7
es8l8yFdvyHx/hgKXlenHrIC63/6jW+pVlhOB5nfSKUPTLu4Ug7ViJTAtVLS0iMU
O1ohOUGasmHXoTgjPYZ3eCBAJJkn5PfLeWS3/7TOusUZ+8HX1KMuou/pOOv9PHF7
Eo/p32/Cf28HePWl2p1l16rLBTlahtBKIeF+S10tWbgvI+bLYk8EJf+gcJCBXfDX
vIdQ8xdYdbBvApK+RvrIChfSC986eelhnQGBe5bC9MyErA+dj2A76D7N43iLU7WM
wi0VjiTlMeDJqVov0glQw7v5aLH2bgvAjgKl9ag9/4rMCr1y32GmNm2Cdj7GN3mK
pTCl4jjgsfRxVmfSKZJwkNjHl9/3IoHZW/bU1W+/iDxfuGRry9VUjHvGrlzy5JcO
R6nmYFCvklC0Cd5Z7N3YyZQcEkE6vAA1a/oOYPGbm1siSQ4dB8/gYE5BJ0//qq6O
d82Psgfou7ZQRCRyXwY2BIPfh/9YeF6Hij64ugOB7WSIUusKPL7DDt+4JqIcYKlR
cpgbTXE7z0kE33ZAeakn
=GY1G
-----END PGP SIGNATURE-----

  reply	other threads:[~2016-09-28 14:40 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
2016-09-28 13:55   ` swedebugia
2016-09-28 14:05   ` John Darrington
2016-09-28 14:39     ` Troy Sankey [this message]
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=147507359323.2034.4440394895994902168@what \
    --to=sankeytms@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=john@darrington.wattle.id.au \
    --cc=ngillmann@runbox.com \
    /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).