all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Nils Gillmann <ng0@n0.is>
Cc: Ricardo Wurmus <rekado@elephly.net>, 32634@debbugs.gnu.org
Subject: [bug#32634] RFC: Process build output
Date: Sat, 08 Sep 2018 19:03:47 +0200	[thread overview]
Message-ID: <875zzfdiq4.fsf@tobias.gr> (raw)
In-Reply-To: <20180908161143.aonygx4iqnj2zury@abyayala>

ng0,

Nils Gillmann wrote:
> Would it make sense to use 'GUIX_UI_NO_COLOR' instead? This 
> makes it
> clear what it is for (use clear function names), and it does not
> impose using "no colors" in other terminal applications if you
> permanently export it.

Note that the (putative) point of the NO_COLORS[0] standard is to 
work *across* project boundaries.

Kind regards,

T G-R

[0]: http://no-color.org/

  parent reply	other threads:[~2018-09-08 17:19 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04 15:29 [bug#32634] RFC: Process build output Ricardo Wurmus
2018-09-04 15:32 ` [bug#32634] [PATCH 1/2] ui: Add support for colorization Ricardo Wurmus
2018-09-04 15:32   ` [bug#32634] [PATCH 2/2] ui: Add soft port for styling and filtering build output Ricardo Wurmus
2018-09-08  9:49     ` Danny Milosavljevic
2018-09-09 21:22       ` bug#32634: " Ricardo Wurmus
2018-09-10 13:17     ` [bug#32634] " Ludovic Courtès
2018-09-10 14:28       ` Ludovic Courtès
2018-09-08  8:32   ` [bug#32634] [PATCH 1/2] ui: Add support for colorization Danny Milosavljevic
2018-09-08 16:11 ` [bug#32634] RFC: Process build output Nils Gillmann
2018-09-08 16:58   ` Tobias Geerinckx-Rice
2018-09-08 17:03   ` Tobias Geerinckx-Rice [this message]
2018-09-09 12:32 ` Danny Milosavljevic
2018-09-09 16:26   ` Ricardo Wurmus
2018-09-10 14:39 ` 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

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

  git send-email \
    --in-reply-to=875zzfdiq4.fsf@tobias.gr \
    --to=me@tobias.gr \
    --cc=32634@debbugs.gnu.org \
    --cc=ng0@n0.is \
    --cc=rekado@elephly.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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.