From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: nnmail-split-fancy-with-parent usage is unclear
Date: 03 Jan 2001 13:05:30 +0100 [thread overview]
Message-ID: <vafpui4j0xh.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <m3elynb8cm.fsf@onyx.nimbus.northernlight.com>
On 01 Jan 2001, Ted Zlatanov wrote:
> How do I use nnmail-split-fancy-with-parent (in nnmail.el)?
The node `Fancy Mail Splitting' in the Gnus info file has the
following text in the current version. Does that give enough info?
/----
| `nnmail-split-fancy-with-parent' is a function which allows you to
| split followups into the same groups their parents are in. Sometimes
| you can't make splitting rules for all your mail. For example, your
| boss might send you personal mail regarding different projects you are
| working on, and as you can't tell your boss to put a distinguishing
| string into the subject line, you have to resort to manually moving the
| messages into the right group. With this function, you only have to do
| it once per thread.
|
| To use this feature, you have to set `nnmail-treat-duplicates' to a
| non-nil value. And then you can include
| `nnmail-split-fancy-with-parent' using the colon feature, like so:
| (setq nnmail-split-fancy
| '(| (: nnmail-split-fancy-with-parent)
| ;; other splits go here
| ))
|
| This feature works as follows: when `nnmail-treat-duplicates' is
| non-nil, Gnus records the message id of every message it sees in the
| file specified by the variable `nnmail-message-id-cache-file', together
| with the group it is in (the group is omitted for non-mail messages).
| When mail splitting is invoked, the function
| `nnmail-split-fancy-with-parent' then looks at the References (and
| In-Reply-To) header of each message to split and searches the file
| specified by `nnmail-message-id-cache-file' for the message ids. When
| it has found a parent, it returns the corresponding group name. It is
| recommended that you set `nnmail-message-id-cache-length' to a somewhat
| higher number than the default so that the message ids are still in the
| cache. (A value of 5000 appears to create a file some 300 kBytes in
| size.) When `nnmail-cache-accepted-message-ids' is non-nil, Gnus also
| records the message ids of moved articles, so that the followup
| messages goes into the new group.
\----
If this doesn't give the info, the manual should be fixed. (Also,
the function itself should be documented, I guess. Hm.)
kai
--
~/.signature
next prev parent reply other threads:[~2001-01-03 12:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-01 15:27 Ted Zlatanov
2001-01-03 12:05 ` Kai Großjohann [this message]
2001-01-03 14:29 ` Ted Zlatanov
2001-01-04 17:29 ` nnimap-split-fancy-with-parent? David S. Goldberg
2001-01-04 18:30 ` nnimap-split-fancy-with-parent? Kai Großjohann
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=vafpui4j0xh.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.org \
/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).