From: Jonas Steverud <tvrud@bredband.net>
Subject: Re: Terminology
Date: Sun, 18 Apr 2004 22:28:01 +0200 [thread overview]
Message-ID: <m2hdvhm3ou.fsf@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se> (raw)
In-Reply-To: <iluekqlm47n.fsf@latte.josefsson.org> (Simon Josefsson's message of "Sun, 18 Apr 2004 22:16:44 +0200")
Simon Josefsson <jas@extundo.com> writes:
> Jonas Steverud <tvrud@bredband.net> writes:
[...]
>> 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.)
The main idea was not to introduce new terms but rename old, confusing ones.
The name "visited" I got from the Emacs terminology of visited
files. A consistent terminology that I personally like.
>> 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.
OK, I didn't know ticked articles counted as read. Doesn't matter
much, remove "I.e. not ticked etc." from my text above. :-)
>> 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.
I didn't talk of specific marks that Gnus keeps track of, I was more
concerned about the terminology - classifications of articles.
Previous mails has indicated that there are some confusion regarding
what we call an article - sometimes regardless of the actual marks of
it and sometimes the marks are considered - and I just tries to see if
we can do something about that confusion. Renaming some of the terms
might help.
>> Unseen: (?) Articles that are unvisited but not shown in the summary
>> buffer, usually expunged articles due to scoring.
>
> "unseen" is another Gnus mark,
I didn't know that. Makes things a little more complicated then.
--
( 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 20:28 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 ` Terminology Simon Josefsson
2004-04-18 20:28 ` Jonas Steverud [this message]
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=m2hdvhm3ou.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).