From: Josh Huber <huber@alum.wpi.edu>
Subject: Re: letting split rules have access to the message body...
Date: 14 May 2001 15:13:41 -0400 [thread overview]
Message-ID: <87bsovlp5m.fsf@mclinux.com> (raw)
In-Reply-To: <vaf4rurzei7.fsf@lucy.cs.uni-dortmund.de>
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Stupid me. There should be a save-excursion and a switch to
> gnus-original-article-buffer in there, I think.
You're absolutely right. Thanks for the tip.
it would be nice if that sequence was documented in the manual. i.e.:
"If you want access to the full message body in a function called from
a split rule, you'll have to do the following:
(save-excursion
(set-buffer gnus-original-article-buffer)
...
)
"
Thanks,
--
Josh Huber
next prev parent reply other threads:[~2001-05-14 19:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 21:30 Josh Huber
2001-05-11 13:20 ` Josh Huber
2001-05-11 22:50 ` Kai Großjohann
2001-05-14 19:13 ` Josh Huber [this message]
2001-05-14 20:16 ` Kai Großjohann
2001-05-14 21:18 ` Josh Huber
2001-05-15 9:24 ` Kai Großjohann
2001-05-15 16:33 ` 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=87bsovlp5m.fsf@mclinux.com \
--to=huber@alum.wpi.edu \
/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).