Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Subject: Re: Terminology
Date: Sun, 18 Apr 2004 22:16:44 +0200	[thread overview]
Message-ID: <iluekqlm47n.fsf@latte.josefsson.org> (raw)
In-Reply-To: <m2llktm565.fsf_-_@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se>

Jonas Steverud <tvrud@bredband.net> writes:

> Dan Christensen <jdc@uwo.ca> writes:
>
> [...]
>> The last two lines seem to contradict the first line, so maybe there
>> is no strict definition of what "unread" means.
>
> Seems like it is time IMHO for some spring cleaning...?
>
> It seems like the big problem is the terms "read" and "unread" that is
> the problem.
>
> Suggested new terms/definitions:
>  Visited: A article that the user has seen before; read, ticked,
>           dormant, marked as expireable, ... (Other criteria?)

I'm not sure we need to introduce more terms...  (But we could keep
the term "visited" around for when we need a new class of read marks.)

>  Read: An article that has been marked as killed, ancient, read in the
>        naïve sense; i.e. actually *read*, ... I.e. not ticked etc.

There is a Gnus mark called "read".  If you tick an active article, it
will become read automatically.  Same for if you mark an article as
expired, etc.

>  Unvisted or Unread: Replaces Unseen which I find confusing - an
>                      article that is killed and yanked from the
>                      summary buffer is in my view unseen.

"Unread" is not a proper Gnus mark.  It might help understanding if
you think of "unread" as an implicit mark, i.e. one that holds if
nothing else holds.  So an article can't be marked both expired and
unread, as unread isn't a mark.  "unread" is just an absence of marks.
Of course, the exception to that rule is the "unseen" mark.

>  Unseen: (?) Articles that are unvisited but not shown in the summary
>          buffer, usually expunged articles due to scoring.

"unseen" is another Gnus mark, it is maintained by Gnus internally and
you can't set/clear it.  Its purpose is to let you know which messages
you have never seen before.  This is not the same as "unread", as you
can M-u an article to make it "unread" (but not "unseen").  "Unread"
articles may be "seen", but "unseen" articles cannot be "read".

IIRC, that is.




  reply	other threads:[~2004-04-18 20:16 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-31  9:05 Configuring spam.el: A few questions 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
2004-04-18 19:56                   ` Terminology (was: Configuring spam.el: A few questions) Jonas Steverud
2004-04-18 20:16                     ` Simon Josefsson [this message]
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=iluekqlm47n.fsf@latte.josefsson.org \
    --to=jas@extundo.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).