public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] [RFC] Portage einfo, elog... output format change
Date: Tue, 28 Sep 2021 17:36:25 +0200	[thread overview]
Message-ID: <62cfb7667569272a355244bd29ae6c30fde01e3c.camel@gentoo.org> (raw)

Hi, everyone.

I know I'm going to regret asking this... but I've prepared a change to
the Portage output format and I think it asks for a wider discussion
than internally in Portage team.

The primary problem with the current output format is that different
kinds of messages differ only in color.  This makes them
indistinguishable without colors and hard to grep.  ago's been asking
for a better way to grep for QA warnings and this is pretty much what
motivated me to do this.

The proposed new format distinguished message types both using colors
and strings.  This is roughly inspired by Xorg logs.  For example,
instead of:

 * some message
 * other message
 * hell if i know what this is

You get:

[WW] some message
[EE] other message
[QA] hell if i know what this is

I've also added more colors to explicitly distinguish einfo from elog,
and ewarn from eqawarn.  Then, I've replaced most of '>>>' and '!!!'
used by Portage with four-character versions to keep messages aligned. 
The 'zings' used for merging files remain three-character, so now it's
easily possible to distinguish messages from installed file list.

The PR doing this is: https://github.com/gentoo/portage/pull/759

Example screenshot:
https://user-images.githubusercontent.com/110765/135119090-16e9599d-1b0f-41b8-a965-a55577183ffd.png

-- 
Best regards,
Michał Górny




             reply	other threads:[~2021-09-28 15:36 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-28 15:36 Michał Górny [this message]
2021-09-28 15:41 ` [gentoo-dev] [RFC] Portage einfo, elog... output format change Wolfgang E. Sanyer
2021-09-28 16:26 ` Ulrich Mueller
2021-09-28 16:37   ` Michał Górny
2021-09-28 17:23     ` Ulrich Mueller
2021-09-28 23:17       ` Hank Leininger
2021-09-29 21:52 ` A Schenck
2021-09-29 22:58   ` Francesco Riosa
2021-10-02  1:32     ` A Schenck
2021-09-29 23:01   ` Sam James
2021-10-02  7:22   ` Ulrich Mueller
2021-10-02 22:04     ` Ionen Wolkens
2021-10-03  2:53       ` Ionen Wolkens
2021-10-03  3:03         ` Ionen Wolkens
2021-10-03  6:58           ` Fabian Groffen
2021-10-03  7:38             ` Ionen Wolkens
2021-10-03  8:19             ` Alexey Sokolov
2021-09-30  6:40 ` Fabian Groffen
2021-09-30  6:44   ` Michał Górny
2021-09-30  7:18     ` Fabian Groffen
2021-10-05  7:35       ` Michał Górny
2021-10-05  7:41         ` Fabian Groffen
2021-10-01 18:30     ` A Schenck
2021-10-01 18:32       ` Alec Warner
2021-10-02 17:25         ` A Schenck
2021-10-02 17:51           ` Mike Gilbert
2021-10-05 19:42             ` A Schenck
2021-10-01 22:00   ` Joshua Kinard
2021-10-02  7:08     ` Michał Górny
2021-10-04  6:48 ` Michał Górny
2021-10-05 20:37   ` Rich Freeman

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=62cfb7667569272a355244bd29ae6c30fde01e3c.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox