On Tue, 20 Dec 2005, Steve Greenland wrote:
On 20-Dec-05, 09:56 (CST), Gabor Gombas <[EMAIL PROTECTED]> wrote:
On Tue, Dec 20, 2005 at 08:57:08AM -0600, Steve Greenland wrote:
[1] Dark blue on black. Need I say more?
The reality is that visibility of color combinations is heavily
dependent on all kinds of things that vim can't determine, from the font
being used and the default background color, to the ambient lighting
of the room and the vision capability of the user (not just color
blindness, but very fine variances in the color sensitivity of the user,
or even how tired the person is, which can affect their ability to
focus.) Color really needs to be tuned to the needs of the individual
user.
The color depends a lot more on the monitor in question, rather than the
user. Nearly all of us with full color vision have roughly the same
sensitivity to all colors -- but, monitors of different manufacturers and
of different age vary a lot.
But, it's trivial to fix this issue.
On Linux console, PuTTY and a good deal of terminal emulators:
echo -ne '\e]P40000ff'
(ESC ] P <color num (0..f)> <RRGGBB color code>)
You can put your palette into /etc/issue, bash prompt or anywhere else.
On real xterms, you can mess with X resources.
On gnome-terminal and konsole, you waddle through the GUI.
If you happen to use CRT monitors that are more than a couple years old,
improving the color palette is pretty much a must.
--
/-----------------------\ Shh, be vewy, vewy quiet,
| [EMAIL PROTECTED] | I'm hunting wuntime ewwows!
\-----------------------/
Segmentation fault (core dumped)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
