From: Kris Maglione <bsdaemon@comcast.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Colors and other fun
Date: Wed, 27 Jun 2007 14:03:47 -0400 [thread overview]
Message-ID: <20070627180347.GC28917@kris.home> (raw)
In-Reply-To: <d150ed48f0aeaf6c1b52b77f1b8f1a6c@quintile.net>
[-- Attachment #1: Type: text/plain, Size: 1340 bytes --]
On Wed, Jun 27, 2007 at 06:55:45PM +0100, Steve Simon wrote:
>I changed the selected text colour in sam to a darker grey-green,
>by editing the source. In my defence the default colour is almost
>invisible on my laptops LCD display.
I don't see why you'd need a defense. If the color scheme is
making it harder to do your work, then I don't see how you could
be denounced for changing it. I, personally, have a hard time
distinguishing the background color of the selected text in
acme, possibly because I'm color blind. I sometimes have to get
close to the screen and squint when matching parens and braces.
I should change it.
But that's really pretty minor. When I sit in front of a foreign
linux box and type ls, I usually get a listing in harsh colors,
some of which I need to get closer to the screen and squint just
to make out words. It seems that whenever I see a screenshot of
a curses app, there are bright and harsh colors, usually blues
and reds, and I'm astounded that people can tolerate looking at
them for hours.
That's my only motivation for changing X resources. Plan 9's
color scheme, on the other hand, is generally agreeable, and
I've never really felt much desire to meddle with it.
--
Kris Maglione
To err is human, but to really foul things up requires
a computer.
[-- Attachment #2: Type: application/pgp-signature, Size: 194 bytes --]
next prev parent reply other threads:[~2007-06-27 18:03 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-27 9:37 pavlovetsky
2007-06-27 10:08 ` Lucio De Re
2007-06-27 15:07 ` Rob Pike
2007-06-27 18:26 ` Bakul Shah
2007-06-27 18:35 ` Kris Maglione
2007-06-27 19:09 ` Bakul Shah
2007-06-27 19:24 ` David Leimbach
2007-06-27 19:39 ` Gabriel Diaz
2007-06-27 20:35 ` Bakul Shah
2007-06-27 21:20 ` Jack Johnson
2007-06-29 2:16 ` Bakul Shah
2007-06-27 19:51 ` Francisco J Ballesteros
2007-06-27 21:49 ` Jack Johnson
2007-07-02 8:55 ` Douglas A. Gwyn
2007-06-28 4:42 ` Anant Narayanan
2007-06-28 4:50 ` andrey mirtchovski
2007-06-28 17:30 ` Dave Eckhardt
2007-06-27 15:59 ` andrey mirtchovski
2007-06-27 16:23 ` Lorenzo Fernando Bivens de la Fuente
2007-06-27 17:55 ` Steve Simon
2007-06-27 18:03 ` erik quanstrom
2007-06-27 18:22 ` Rob Pike
2007-06-28 15:26 ` Steve Simon
2007-06-27 18:03 ` Kris Maglione [this message]
2007-06-27 18:59 Russ Cox
2007-06-27 19:13 ` Tim Wiess
2007-06-27 21:25 ` Charles Forsyth
2007-06-27 15:41 ` john
2007-06-27 21:56 ` erik quanstrom
2007-06-27 16:18 ` john
2007-06-27 22:06 ` Kris Maglione
2007-06-27 21:48 ` Markus Sonderegger
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=20070627180347.GC28917@kris.home \
--to=bsdaemon@comcast.net \
--cc=9fans@cse.psu.edu \
/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;
as well as URLs for NNTP newsgroup(s).