Re: color by default

From: Gavin Flower <GavinFlower(at)archidevsys(dot)co(dot)nz>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: color by default
Date: 2020-01-06 07:26:39
Message-ID: 171d92f5-fc29-a207-3db9-c16c63bb2ea7@archidevsys.co.nz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 06/01/2020 18:38, Michael Paquier wrote:
> On Fri, Jan 03, 2020 at 01:10:30PM -0500, Robert Haas wrote:
>> On Thu, Jan 2, 2020 at 6:38 PM Gavin Flower
>> <GavinFlower(at)archidevsys(dot)co(dot)nz> wrote:
>>> I find coloured output very difficult to read, as the colours seem to be
>>> chosen on the basis everyone uses white as the background colour for
>>> terminals -- whereas I use black, as do a lot of other people.
>> I don't like colored output either.
> I don't like colored output either. However there is an easy way to
> disable that so applying this patch does not change things IMO as
> anybody unhappy with colors can just disable it with a one-liner in
> a bashrc or such.
> --
> Michael

That's kind of like using a sledgehammer to crack a nut.

The colour in grep output is often useful.

I'd like to control it per application.

Cheers,
Gavin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2020-01-06 07:31:43 Re: error context for vacuum to include block number (atomic progress update)
Previous Message Michael Paquier 2020-01-06 06:42:39 Re: Add pg_file_sync() to adminpack