From: Jonas Steverud <tvrud@bredband.net>
Subject: Re: Configuring spam.el: A few questions
Date: Fri, 16 Apr 2004 11:42:25 +0200 [thread overview]
Message-ID: <m265c0uum6.fsf@c-ec5372d5.036-4-67626721.cust.bredbandsbolaget.se> (raw)
In-Reply-To: <4n7jwhaug6.fsf@b2-25-3.bwh.harvard.edu> (Ted Zlatanov's message of "Thu, 15 Apr 2004 15:54:01 -0400")
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Sat, 03 Apr 2004, tvrud@bredband.net wrote:
[...]
>> I quite don't understand the difference between the
>> (: gnus-registry-split-fancy-with-parent) and the
>> (: nnmail-split-fancy-with-parent). Anyone that cares to explain the
>> difference and/or the idea behind the registry?
>
> The registry is a way to keep track of articles by message ID, and to
> record in what groups that message ID has been seen. Tracking parent
> articles is done with the References header, which indicates the
> message IDs of parent articles. Article copies, moves, and deletions
> are tracked.
>
> The nnmail-split-fancy-with-parent method was the inspiration, and
> it's quite similar, but it's more limited because it only works for
> nnmail.
I see. One reason for my confusion where the line "This is the
gnus-registry.el package, works with other backends besides nnmail.",
which I interpret as "the registry does not work with nnmail." I later
realises what the "besides" nnmail means in this context. My fault, sorry.
I found a ... bug or flaw, depending on how you see it, in
nnmail-split-fancy-with-parent. If I copy one of you emails to another
group, e.g. nnfolder:ToDo, responses end up in the ToDo group instead
of in the Ding group. In one sense, this is correct behavior but how
do I make it not happen for copied mails? Not that it is a big issue,
I'm just curious.
If I've understood it correctly, nnmail is the mail handling
interface, the front end "Gnus" sees and then it uses a number of
backends like nnfolder to actually store and handle the emails. Right?
I.e. nnmail is not a backend that can replace nnfolder et all.
> "Unseen" are those articles you never saw before.
>
> "Unread" are those that are not marked read, expired, ticked, etc.
This could be added to the Terminology node in the info file (which I
just found) (and which could do with some M-x sort-lines ;-) ). IMHO.
Thank you very much for your help! I will implement this in a matter
of hours, I think. :-D
--
( 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-16 9:42 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 [this message]
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 ` 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=m265c0uum6.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).