Gnus development mailing list
 help / color / mirror / Atom feed
From: David Abrahams <dave@boost-consulting.com>
Subject: Re: Overbearing undownloaded face
Date: Sun, 04 May 2003 20:12:59 -0400	[thread overview]
Message-ID: <ud6iy8d4k.fsf@boost-consulting.com> (raw)
In-Reply-To: <ilun0i2qog4.fsf@latte.josefsson.org> (Simon Josefsson's message of "Mon, 05 May 2003 01:31:07 +0200")

Simon Josefsson <jas@extundo.com> writes:

> David Abrahams <dave@boost-consulting.com> writes:
>
>> Simon Josefsson <jas@extundo.com> writes:
>>
>>> David Abrahams <dave@boost-consulting.com> writes:
>>>
>>>> Simon Josefsson <jas@extundo.com> writes:
>>>>
>>>>> 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?
>>>>
>>>> I'm likin' it, though I don't exactly understand what the effect was.
>>>
>>> For me, it makes unread (and ticked, and ...) articles black instead
>>> of a green-blue-ish (undownloadable mark) color which looks almost
>>> identical to the green-blue-ish color which is used for read messages.
>>
>> That's what it does for me, too.  What I meant was I'm not sure what
>> it's doing *technically*.  If moving those Sexprs down makes them
>> ineffectual, can't they be eliminated?
>
> Ah.  But it still has priority over the read mark.  So if you have a
> read, undownloaded, article it will be marked with the undownloaded
> face instead of the read face.  However, if the article is unread (or
> ticked, or ...), you will see the unread (or tick, or ...) face,
> instead of the undownloaded face.
>
> Wasn't undownloaded articles marked with a @ or % mark or something
> before?  Do people care about the downloadedness of articles?  I
> don't.

I care a little.  I sometimes go away from my network connection and
want to take a record of some conversations with me.


-- 
Dave Abrahams
Boost Consulting
www.boost-consulting.com




  parent reply	other threads:[~2003-05-05  0:12 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
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 [this message]
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=ud6iy8d4k.fsf@boost-consulting.com \
    --to=dave@boost-consulting.com \
    /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).