From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: what's available in fancy-split functions?
Date: 26 Apr 2001 08:20:53 +0200 [thread overview]
Message-ID: <vafk8489o6y.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <878zkoppm6.fsf@mclinux.com> (Josh Huber's message of "25 Apr 2001 18:43:29 -0400")
On 25 Apr 2001, Josh Huber wrote:
> I can't seem to find any documentation mentioning what kind of data
> is available to a function called with a fancy-split rule.
Note the following paragraph in the documentation for
nnmail-split-methods:
/----
| The second element can also be a function. In that case, it will be
| called narrowed to the headers with the first element of the rule as
| the argument. It should return a non-nil value if it thinks that the
| mail belongs in that group.
\----
Sadly, it's not made explicit that this also applies to
nnmail-split-fancy.
But the documentation for nnmail-split-fancy (the variable) does
mention that functions called via `:' are called ``in a buffer
containing the message headers''.
> I'd like to do some special sorting on incoming messages, with the
> form like:
>
> (: my-gnus-filter "mail.junk")
>
> I'm passing in the group which will be returned in certain cases.
>
> Does my function have access to the whole message?
>
> can I:
>
> (save-restriction
> (widen)
> ...
Yes, this has been suggested a couple of weeks ago.
> I guess on the same topic, does gnus have functions for extracting
> particular headers from a message for use in custom user functions?
message-fetch-field?
kai
--
The passive voice should never be used.
next prev parent reply other threads:[~2001-04-26 6:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-25 22:43 Josh Huber
2001-04-26 6:20 ` Kai Großjohann [this message]
2001-04-26 20:40 ` Josh Huber
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=vafk8489o6y.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
/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).