From: Simon Josefsson <jas@extundo.com>
Cc: Joakim Hove <joakim.hove@phys.ntnu.no>, <ding@gnus.org>
Subject: Re: Run an arbitrary function on message after splitting
Date: Thu, 26 Apr 2001 00:21:31 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.33.0104260020080.20292-100000@slipsten.extundo.com> (raw)
In-Reply-To: <vafae5amkiv.fsf@lucy.cs.uni-dortmund.de>
> > access to the full message-body.
>
> I think it has full access. Invoke (debug) at that spot and see what
> is in the full buffer. I think it is sufficient to say
>
> (save-restriction
> (widen)
> ...do.stuff.with.whole.message...)
>
> But I'm not 100% certain.
Nnimap doesn't fetch the entire mail, just the headers. But nnmail
probably got the whole mail. So it depends on the backend...
prev parent reply other threads:[~2001-04-25 22:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-20 20:44 Joakim Hove
2001-04-20 21:07 ` Kai Großjohann
2001-04-20 21:15 ` Joakim Hove
2001-04-20 21:17 ` Joakim Hove
2001-04-21 13:48 ` Kai Großjohann
2001-04-25 22:21 ` Simon Josefsson [this message]
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=Pine.LNX.4.33.0104260020080.20292-100000@slipsten.extundo.com \
--to=jas@extundo.com \
--cc=ding@gnus.org \
--cc=joakim.hove@phys.ntnu.no \
/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).