From: Jonas Steverud <tvrud@bredband.net>
Subject: Terminology (was: Configuring spam.el: A few questions)
Date: Sun, 18 Apr 2004 21:56:02 +0200 [thread overview]
Message-ID: <m2llktm565.fsf_-_@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se> (raw)
In-Reply-To: <87ad19faqt.fsf@uwo.ca> (Dan Christensen's message of "Sun, 18 Apr 2004 13:37:30 -0400")
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?)
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.
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.
Unseen: (?) Articles that are unvisited but not shown in the summary
buffer, usually expunged articles due to scoring.
Maybe Unseen should be considered Visited, i.e. an expunged article is
considered visited. But isn't it a difference between expunge and
mark-and-expunge? (Checks info...) Yes it is. (Actually, what happens
with an article that is expunged but not marked as read? Will it still
count as unread and the group will show unread articles in *Group* buffer?)
I have not given this very much thought but the unread/read and unseen
terms seams a little confusing and maybe it should be replaced by
"visited" or some similar term? Opinions?
--
( http://hem.bredband.net/steverud/ ! Wei Wu Wei )
( Meaning of U2 Lyrics, Roleplaying ! To Do Without Do )
next prev parent reply other threads:[~2004-04-18 19:56 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 ` Jonas Steverud [this message]
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=m2llktm565.fsf_-_@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se \
--to=tvrud@bredband.net \
/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).