public inbox for util-linux@vger.kernel.org
 help / color / mirror / Atom feed
From: Felix Miata <mrmazda@earthlink.net>
To: util-linux@vger.kernel.org
Subject: Re: global fdisk colors disable
Date: Wed, 15 Jan 2014 09:14:30 -0500	[thread overview]
Message-ID: <52D697C6.9000304@earthlink.net> (raw)
In-Reply-To: <52D6552B.6040704@draigBrady.com>

On 2014-01-15 09:30 (GMT) Pádraig Brady composed:

> I think the current mechanism used is best.

What mechanism are you referring to, needing an override switch on every 
invocation on an alien system?

> I.E. default to showing colors when possible but give an option to disable.

$SUBJECT Keyword: global.

> Global env vars come with their own disadvantages.

+1

> However I will say that one has to be careful when using colors,

Exactly.

> and the use in fdisk seems a bit redundant.

I think orthogonal is the better word than redundant.

> I.E. colors are useful
> to distinguish things, like the portion of a match in grep or
> the type of a file in ls. I'm not sure the items distinguished
> in fdisk non obvious and worth the hassle of worrying about color.

Indeed.
-- 
"The wise are known for their understanding, and pleasant
words are persuasive." Proverbs 16:21 (New Living Translation)

  Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!

Felix Miata  ***  http://fm.no-ip.com/

  parent reply	other threads:[~2014-01-15 14:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-15  6:47 global fdisk colors disable Felix Miata
2014-01-15  8:27 ` Karel Zak
2014-01-15  9:30   ` Pádraig Brady
2014-01-15 10:24     ` Karel Zak
2014-01-15 14:14     ` Felix Miata [this message]
2014-01-15 14:10   ` Felix Miata
2014-01-15 15:21     ` Mike Frysinger
2014-01-16  9:24       ` Felix Miata
2014-01-16  9:59         ` Karel Zak
2014-01-15 17:11     ` Karel Zak
2014-01-16  9:06       ` Felix Miata

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=52D697C6.9000304@earthlink.net \
    --to=mrmazda@earthlink.net \
    --cc=util-linux@vger.kernel.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