From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: Possible SpamAssassin node info documentation error.
Date: Thu, 04 Dec 2003 11:32:03 -0500 [thread overview]
Message-ID: <4n7k1ck0ho.fsf@lockgroove.bwh.harvard.edu> (raw)
In-Reply-To: <878yltsdw5.fsf@zip.com.au> (Kevin Ryde's message of "Thu, 04 Dec 2003 09:03:06 +1000")
On Thu, 04 Dec 2003, user42@zip.com.au wrote:
> Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
>>
>> (defun kevin-spamassassin ()
>> (save-excursion
>> (widen)
>
> Should there be a save-restriction too, or does gnus not care about
> that once it gets to the splitting stage?
I added save-restriction in this example and the other one (in Fancy
Mail Splitting). Thanks!
Ted
next prev parent reply other threads:[~2003-12-04 16:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-15 19:31 Rob Browning
2003-10-15 19:42 ` Rob Browning
2003-10-16 14:52 ` Ted Zlatanov
2003-10-16 13:42 ` Lars Magne Ingebrigtsen
2003-12-03 23:03 ` Kevin Ryde
2003-12-04 16:32 ` Ted Zlatanov [this message]
2003-10-16 14:50 ` Ted Zlatanov
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=4n7k1ck0ho.fsf@lockgroove.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--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).