Gnus development mailing list
 help / color / mirror / Atom feed
From: Greg Troxel <gdt@work.lexort.com>
To: ding@gnus.org
Subject: Re: message-header-xheader unused, maybe
Date: Tue, 22 May 2007 08:55:57 -0400	[thread overview]
Message-ID: <smud50t586a.fsf@linuxpal.mit.edu> (raw)
In-Reply-To: <b4m4pm5ceiv.fsf@jpl.org> (Katsumi Yamaoka's message of "Tue, 22 May 2007 19:56:56 +0900")

  I use light.  But I tried the white-on-black Emacs today and
  realized I can do nothing in the message header unless I turn
  the brightness of the display up to practically the maximum.  It
  is similar also in the article buffer.  (It might be because I
  usually dim the display too much, though.)  OTOH, emacs-w3m does
  not cause me inconvenience.

I have long used white text on black background, and used to use green
text on black background to avoid fuzz from convergence issues.
I have in .Xresources:

*Background:	black
*Foreground:	white

In a X11 emacs, the colors have not been too annoying, but they are
still darker than I would like.  With emacs running in an xterm, I find
the colors, particularly for quoted text in article display, to be very
dark, to the point where I turn off font-lock-mode to be able to read.

Part of the issue may be the values reported by tty-color-alist in
xterm (NetBSD, XFree86).

(("black" 0 0 0 0)
 ("red" 1 65535 0 0)
 ("green" 2 0 65535 0)
 ("yellow" 3 65535 65535 0)
 ("blue" 4 0 0 65535)
 ("magenta" 5 65535 0 65535)
 ("cyan" 6 0 65535 65535)
 ("white" 7 65535 65535 65535))

In my view the right colors would have high luminances and therefore not
be that saturated.  I mean a light blue like c0c0ff rather than 0000ff.

I don't know that the right fix is.  Perhaps not using color should be
chosen if the palette is inadequate.  Perhaps I should get a spiffier
xterm.







  reply	other threads:[~2007-05-22 12:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-18  1:25 Kevin Ryde
2007-05-22 10:56 ` Katsumi Yamaoka
2007-05-22 12:55   ` Greg Troxel [this message]
2007-05-25  9:31     ` Katsumi Yamaoka
2007-05-26  1:37     ` Kevin Ryde

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=smud50t586a.fsf@linuxpal.mit.edu \
    --to=gdt@work.lexort.com \
    --cc=ding@gnus.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;
as well as URLs for NNTP newsgroup(s).