Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: Overbearing undownloaded face
Date: Fri, 02 May 2003 14:24:25 +0200	[thread overview]
Message-ID: <iluhe8dh6yu.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m2d6j2qfs7.fsf@sbcglobal.net> (Harry Putnam's message of "Thu, 01 May 2003 18:49:12 -0700")

Harry Putnam <hgp@sbcglobal.net> writes:

> I've recently come back to using the agent after several mnths of
> running plugged only.  The current setup with undownloaded face seems
> to overpower other long standing faces and options.

Yup.  I've been using this, perhaps the defaults should be changed?
Currently undownloadable marks is more important than, say, tick
marks, which doesn't seem right to me.  And I was used to the black
marks on unread messages.

I sent a message asking for opinions about this a few months ago, but
now that I try to find my message, I note that it contained a screen
shot so it was probably rejected due to size.  So:  Opinions?

--- gnus-sum.el.~6.342.~	Tue Apr 29 02:44:20 2003
+++ gnus-sum.el	Fri May  2 14:16:54 2003
@@ -902,12 +902,6 @@
 (defcustom gnus-summary-highlight
   '(((eq mark gnus-canceled-mark)
      . gnus-summary-cancelled-face)
-    ((and uncached (> score default-high))
-     . gnus-summary-high-undownloaded-face)
-    ((and uncached (< score default-low))
-     . gnus-summary-low-undownloaded-face)
-    (uncached
-     . gnus-summary-normal-undownloaded-face)
     ((and (> score default-high)
 	  (or (eq mark gnus-dormant-mark)
 	      (eq mark gnus-ticked-mark)))
@@ -935,6 +929,12 @@
      . gnus-summary-high-read-face)
     ((< score default-low)
      . gnus-summary-low-read-face)
+    ((and uncached (> score default-high))
+     . gnus-summary-high-undownloaded-face)
+    ((and uncached (< score default-low))
+     . gnus-summary-low-undownloaded-face)
+    (uncached
+     . gnus-summary-normal-undownloaded-face)
     (t
      . gnus-summary-normal-read-face))
   "*Controls the highlighting of summary buffer lines.




  parent reply	other threads:[~2003-05-02 12:24 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-02  1:49 Harry Putnam
2003-05-02  1:54 ` Henrik Enberg
2003-05-02  2:37   ` Harry Putnam
2003-05-02  4:01     ` Kevin Greiner
2003-05-02  5:37       ` Harry Putnam
2003-05-04 23:12       ` Harry Putnam
2003-05-05 14:19         ` Kevin Greiner
2003-05-05 14:50         ` Kai Großjohann
2003-05-06 16:37           ` Kai Großjohann
2003-05-02 12:24 ` Simon Josefsson [this message]
2003-05-02 16:19   ` Lars Magne Ingebrigtsen
2003-05-02 18:09     ` David S Goldberg
2003-05-02 21:02       ` Kevin Greiner
2003-05-03  1:11         ` Harry Putnam
2003-05-03 16:45         ` Kai Großjohann
2003-05-05 13:48         ` David S Goldberg
2003-05-09 19:54         ` Gleb Arshinov
2003-05-02 23:11     ` Harry Putnam
2003-05-03 16:43       ` Kai Großjohann
2003-05-04  0:11         ` Harry Putnam
2003-05-04 13:21           ` Kai Großjohann
2003-05-02 23:16     ` Simon Josefsson
2003-05-02 21:12   ` Kevin Greiner
2003-05-02 23:24     ` Simon Josefsson
2003-05-03  1:16     ` Harry Putnam
2003-05-04 16:57   ` David Abrahams
2003-05-04 20:15     ` Simon Josefsson
2003-05-04 23:10       ` David Abrahams
2003-05-04 23:31         ` Simon Josefsson
2003-05-04 23:46           ` Harry Putnam
2003-05-05 15:08             ` Kevin Greiner
2003-05-06  0:53               ` Harry Putnam
2003-05-05  0:12           ` David Abrahams
2003-05-05 14:56           ` Kai Großjohann

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=iluhe8dh6yu.fsf@latte.josefsson.org \
    --to=jas@extundo.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).