* Colors and progress indicators on buildprocesses
@ 2016-09-28 9:38 swedebugia
2016-09-28 9:57 ` ng0
2016-09-30 20:41 ` Ludovic Courtès
0 siblings, 2 replies; 6+ messages in thread
From: swedebugia @ 2016-09-28 9:38 UTC (permalink / raw)
To: guix-devel
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?
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Colors and progress indicators on buildprocesses
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-30 20:41 ` Ludovic Courtès
1 sibling, 2 replies; 6+ messages in thread
From: ng0 @ 2016-09-28 9:57 UTC (permalink / raw)
To: swedebugia, guix-devel
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
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Colors and progress indicators on buildprocesses
2016-09-28 9:57 ` ng0
@ 2016-09-28 13:55 ` swedebugia
2016-09-28 14:05 ` John Darrington
1 sibling, 0 replies; 6+ messages in thread
From: swedebugia @ 2016-09-28 13:55 UTC (permalink / raw)
To: ng0; +Cc: guix-devel
On 2016-09-28 11:57, ng0 wrote:
> 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.
I understand.
What I proposed was not to color the logs but the output of guix (to
distinguish it from the rest) telling the user what it is going to
do/doing.
The proposal for percentage did not include coloring.
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Colors and progress indicators on buildprocesses
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
1 sibling, 1 reply; 6+ messages in thread
From: John Darrington @ 2016-09-28 14:05 UTC (permalink / raw)
To: ng0; +Cc: guix-devel
[-- Attachment #1: Type: text/plain, Size: 687 bytes --]
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.
J'
--
Avoid eavesdropping. Send strong encrypted email.
PGP Public key ID: 1024D/2DE827B3
fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3
See http://sks-keyservers.net or any PGP keyserver for public key.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Colors and progress indicators on buildprocesses
2016-09-28 14:05 ` John Darrington
@ 2016-09-28 14:39 ` Troy Sankey
0 siblings, 0 replies; 6+ messages in thread
From: Troy Sankey @ 2016-09-28 14:39 UTC (permalink / raw)
To: John Darrington, ng0; +Cc: guix-devel
[-- 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-----
^ permalink raw reply [flat|nested] 6+ messages in thread
* Re: Colors and progress indicators on buildprocesses
2016-09-28 9:38 Colors and progress indicators on buildprocesses swedebugia
2016-09-28 9:57 ` ng0
@ 2016-09-30 20:41 ` Ludovic Courtès
1 sibling, 0 replies; 6+ messages in thread
From: Ludovic Courtès @ 2016-09-30 20:41 UTC (permalink / raw)
To: swedebugia; +Cc: guix-devel
Hi!
swedebugia@riseup.net skribis:
> 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?
I think these are all good ideas. Especially colors, which could help a
lot (for non-Emacs terminals at least), and provide a more pleasant
experience.
Ludo’.
^ permalink raw reply [flat|nested] 6+ messages in thread
end of thread, other threads:[~2016-10-04 12:49 UTC | newest]
Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
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
2016-09-30 20:41 ` Ludovic Courtès
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).