From: Felix Miata <mrmazda@earthlink.net>
To: util-linux@vger.kernel.org
Subject: Re: global fdisk colors disable
Date: Thu, 16 Jan 2014 04:06:02 -0500 [thread overview]
Message-ID: <52D7A0FA.8010303@earthlink.net> (raw)
In-Reply-To: <20140115171128.GM12700@x2.net.home>
On 2014-01-15 18:11 (GMT+0100) Karel Zak composed:
> On Wed, Jan 15, 2014 at 09:10:19AM -0500, Felix Miata wrote:
>> Orange on a 16 color display doesn't look much different than red. Both
>> contrast poorly unless the background is white, detracting from any value as
>> warning intended by those color choices.
> so your suggestion is to disable the colors at all for all Linux boxes by
> default?
I've been using white on blue text modes for nearly 3 decades, ever since I
learned to use ansi to set screen colors in DOS 3, as I find white on black
rather unpleasant to need to use more than occasionally.
Probably better to have some option for a user or admin to force the ttys
into 2 or 4 color mode regardless whether the system is capable of or
happiest with 8, 15, 16, 24 or more.
> I understand your point of view, but I'd like to use default that is
> usable to majority of the Linux users.
That is a typical majority rule effect. The problem is those with poorer than
average vision by definition are both a minority and handicapped. From that
it apparently follows that making it more difficult for the minority already
handicapped must be OK because the majority of average or better people might
enjoy some colors that may or may not make sense or provide real enhancement.
>> One reason I use the ttys is for comfort, a pleasant environment where
>> legibility is maximized, in part by big bold text, in part by lack of
>> distraction from other windows and widgets, in other part by using only the
>> two colors of my choice. In that environment I don't want or need to be
>> "warned" by colors I can barely see.
> I understand.. it would be nice to have a one place to disable/enable
> colors for all terminal utils, maybe something like
> /etc/terminal-colors.d/[<utilname>.]disable
> I'm going to resolve the problem for the next v2.25. Thanks!
Thank you! This sounds like it should be a good option for many.
--
"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/
prev parent reply other threads:[~2014-01-16 9:06 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
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 [this message]
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=52D7A0FA.8010303@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