Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
Cc: ding@gnus.org
Subject: Re: Configuring spam.el: A few questions
Date: Sun, 18 Apr 2004 13:37:30 -0400	[thread overview]
Message-ID: <87ad19faqt.fsf@uwo.ca> (raw)
In-Reply-To: <87y8otogpa.fsf@emptyhost.emptydomain.de> (Kai Grossjohann's message of "Sun, 18 Apr 2004 10:04:01 +0200")

Kai Grossjohann <kai@emptydomain.de> writes:

> Dan Christensen <jdc@uwo.ca> writes:
>
>> Ted Zlatanov <tzz@lifelogs.com> writes:
>>
>>> "Unread" are those that are not marked read, expired, ticked, etc.
>>
>> Hmm, isn't an expired article considered "read"?
>
> It is quite confusing that "read" is used as a category (read versus
> unread) but also as a specific mark that is part of the "read"
> category.

Yes, it is confusing, and I was confused.  In fact, I meant to say
"isn't a ticked article considered unread?"  I saw expired and ticked
grouped together and thought that one of them must be wrong, but I
think it is ticked that is wrong.  Right? ... Fumbles through the info
pages...  Hmm, from the node called (not surprisingly) "Unread
Articles", we have

|    The following marks mark articles as (kinda) unread, in one form or
| other.
| 
| `!'
|      Marked as ticked (`gnus-ticked-mark').
| 
...
| 
| `?'
|      Marked as dormant (`gnus-dormant-mark').
| 
...
| 
| `SPACE'
|      Marked as unread (`gnus-unread-mark').
| 
|      "Unread articles" are articles that haven't been read at all yet.

The last two lines seem to contradict the first line, so maybe there
is no strict definition of what "unread" means.

Dan



  reply	other threads:[~2004-04-18 17:37 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31  9:05 Jonas Steverud
2004-03-31 18:54 ` Ted Zlatanov
2004-04-03 11:57   ` Jonas Steverud
2004-04-15 19:54     ` Ted Zlatanov
2004-04-16  9:42       ` Jonas Steverud
2004-04-16 14:36         ` Ted Zlatanov
2004-04-16 20:37           ` Kai Grossjohann
2004-04-17  9:28           ` Jonas Steverud
2004-04-17 18:55             ` Dan Christensen
2004-04-18  8:04               ` Kai Grossjohann
2004-04-18 17:37                 ` Dan Christensen [this message]
2004-04-18 19:56                   ` Terminology (was: Configuring spam.el: A few questions) Jonas Steverud
2004-04-18 20:16                     ` Terminology Simon Josefsson
2004-04-18 20:28                       ` Terminology Jonas Steverud
2004-04-18 20:50                         ` Terminology Simon Josefsson
2004-04-19  8:13                           ` Terminology Kai Grossjohann
2004-04-21 15:50                             ` Terminology Ted Zlatanov
2004-04-18 20:30                   ` Configuring spam.el: A few questions Kai Grossjohann

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=87ad19faqt.fsf@uwo.ca \
    --to=jdc@uwo.ca \
    --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).