Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <simon@josefsson.org>
Subject: Re: more on accessing the body via split rules...
Date: 21 May 2001 19:29:59 +0200	[thread overview]
Message-ID: <ilulmnq7gq0.fsf@barbar.josefsson.org> (raw)
In-Reply-To: <871ypi7q10.fsf@mclinux.com> (Josh Huber's message of "21 May 2001 10:08:59 -0400")

Josh Huber <huber@alum.wpi.edu> writes:

> > If this would happen, that would be good enough, I guess.  Then, split
> > rules wishing to access the message body can look in
> > nnmail-incoming-buffer.
> > 
> > Josh?
> 
> It doesn't happen.  I put a (debug) inside my fancy split function,
> and checked out the values of the variables and what buffers existed.
> gnus-original-article-buffer definitely points to < *Original
> Article*> and said buffer contains the message being re-spooled.
> 
> Should it copy the message into nnmail-incoming-buffer beforehand?

Yes, and looking at the code it looks like it does, but maybe I'm
reading it wrong.  The article would be in g-o-a-b as well.



  parent reply	other threads:[~2001-05-21 17:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-18 15:15 Josh Huber
2001-05-18 15:37 ` Josh Huber
2001-05-18 16:12   ` Kai Großjohann
2001-05-18 16:33     ` Josh Huber
2001-05-18 16:56       ` Kai Großjohann
2001-05-18 18:58         ` Josh Huber
2001-05-18 19:16           ` Kai Großjohann
2001-05-18 20:35             ` Josh Huber
2001-05-18 22:44               ` Kai Großjohann
2001-05-18 21:07             ` Simon Josefsson
2001-05-18 22:43               ` Kai Großjohann
2001-05-19  8:58                 ` Simon Josefsson
2001-05-19 11:20                   ` Kai Großjohann
2001-05-21 14:08                     ` Josh Huber
2001-05-21 14:30                       ` Kai Großjohann
2001-05-21 14:34                         ` Josh Huber
2001-05-21 17:29                       ` Simon Josefsson [this message]
2001-05-21 18:15                         ` 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=ilulmnq7gq0.fsf@barbar.josefsson.org \
    --to=simon@josefsson.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).