Gnus development mailing list
 help / color / mirror / Atom feed
From: Emerick Rogul <emerick@cs.bu.edu>
Subject: Re: automatic Agentizing of servers (was: Summary buffer
Date: Mon, 24 Nov 2003 12:05:29 -0500	[thread overview]
Message-ID: <vuosmkdg0iu.fsf@csa.bu.edu> (raw)
In-Reply-To: <uptfhyar1.fsf@xpediantsolutions.com> (Kevin Greiner's message of "Mon, 24 Nov 2003 10:47:14 -0600")

Kevin Greiner writes:

> Well, first the agent doesn't enable inverse video.  It changes the
> header's foreground color to cyan (unless you changed that
> locally).

Actually, notice the final clause in this (and the other defface's for
gnus-summary-*-downloaded-face):

(defface gnus-summary-normal-undownloaded-face
   '((((class color)
       (background light))
      (:foreground "cyan4" :bold nil))
     (((class color) (background dark))
      (:foreground "LightGray" :bold nil))
     (t (:inverse-video t)))
  "Face used for normal interest uncached articles.")

Personally, I find this setting to be a serious eye strain and I would
argue against it being the default.  But at least now I understand
what settings I need to twiddle to disable it.

-Emerick
-- 
-------------------------------------------------------------------------
Emerick Rogul             /\/     "how young are you, how old am i?
emerick@cs.bu.edu         /\/      let's count the rings around my eyes."
------------------------------------------------- 'i will dare', the mats



  reply	other threads:[~2003-11-24 17:05 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-24 15:14 Summary buffer highlighting Emerick Rogul
2003-11-24 16:17 ` automatic Agentizing of servers (was: Summary buffer highlighting) Ted Zlatanov
2003-11-24 16:42   ` automatic Agentizing of servers (was: Summary buffer Emerick Rogul
2003-11-24 16:47   ` Kevin Greiner
2003-11-24 17:05     ` Emerick Rogul [this message]
2003-11-24 17:07     ` Ted Zlatanov
2003-11-25  2:48       ` Kevin Greiner
2003-11-25  8:25         ` Simon Josefsson
2003-11-25 18:31           ` Ted Zlatanov
2003-12-29 21:22           ` Steinar Bang
2003-12-29 21:39             ` Simon Josefsson
2003-12-29 21:58               ` Steinar Bang
2003-12-29 22:23                 ` Steinar Bang
2003-12-29 22:27                   ` Steinar Bang
2003-12-29 22:36                     ` Steinar Bang
2003-12-29 22:33                 ` Simon Josefsson
2003-12-29 22:44                   ` Steinar Bang
2003-12-29 23:00                     ` Simon Josefsson
2003-12-29 23:10                       ` Kevin Greiner
2003-12-29 23:17                         ` Simon Josefsson
2003-12-29 23:37                           ` Kevin Greiner
2003-12-29 23:53                             ` Simon Josefsson
2003-12-30  2:19                               ` Harry Putnam
2003-12-30  9:44                                 ` Steinar Bang
2003-12-30 11:16                                 ` Simon Josefsson
2003-12-30 20:55                                   ` Steinar Bang
2003-12-30 21:30                                     ` Simon Josefsson
2003-12-30 22:49                                       ` Harry Putnam
2003-12-31 12:55                                       ` Steinar Bang
2003-12-30  9:40                       ` Steinar Bang

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=vuosmkdg0iu.fsf@csa.bu.edu \
    --to=emerick@cs.bu.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).