From: "Ted Zlatanov" <tzz@lifelogs.com>
Subject: Re: Split based on threads?
Date: 21 Jun 2004 13:35:58 -0400 [thread overview]
Message-ID: <4nvfhkstj5.fsf@lifelogs.com> (raw)
In-Reply-To: <v9eko89adk.fsf@marauder.physik.uni-ulm.de> (Reiner Steib's message of "Mon, 21 Jun 2004 17:52:23 +0200")
On Mon, 21 Jun 2004, 4.uce.03.r.s@nurfuerspam.de wrote:
On Mon, Jun 21 2004, Ted Zlatanov wrote: > On Sat, 19 Jun 2004, harder@ifa.au.dk wrote:
> [...]
>>> There's also `nnmail-split-fancy-with-parent'
>>> <info://gnus/Fancy+Mail+Splitting> -- I don't how it differs from the
>>> registry version.
>>
>> nnmail-s-f-w-p doesn't track article copy/move/delete operations, and
>> only works for nnmail.
>
> I think it's supposed to work for copy and move:
>
> ,----[ C-h v nnmail-cache-accepted-message-ids RET ]
> | nnmail-cache-accepted-message-ids's value is t
> |
> | Documentation:
> | If non-nil, put Message-IDs of Gcc'd articles into the duplicate cache.
> | If non-nil, also update the cache when copy or move articles.
> `----
Sorry, my mistake. nnmail-s-f-w-p tracks those operations inside
nnmail only. It doesn't track nnmail to nnimap, for instance
(IIRC). I believe this was the main reason why I wrote the registry,
to make it work across all backends.
Ted
next prev parent reply other threads:[~2004-06-21 17:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-18 20:12 Norman Walsh
2004-06-18 21:17 ` Chris Green
2004-06-18 22:49 ` Jesper Harder
2004-06-21 14:39 ` Ted Zlatanov
2004-06-21 15:52 ` Reiner Steib
2004-06-21 17:35 ` Ted Zlatanov [this message]
2004-06-24 14:17 ` Kai Grossjohann
2004-06-24 14:43 ` Reiner Steib
2004-06-24 16:06 ` Ted Zlatanov
2004-06-25 6:23 ` Kai Grossjohann
2004-06-21 14:43 ` Ted Zlatanov
2004-06-18 21:20 ` Jonas Steverud
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=4nvfhkstj5.fsf@lifelogs.com \
--to=tzz@lifelogs.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).