Re: letting split rules have access to the message body...

[Josh Huber <huber@alum.wpi.edu>]

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> It seems this has been done, at least in CVS:
> 
> /----[ from the Gnus info file, node `Fancy Mail Splitting' ]
> |   6. `(: FUNCTION ARG1 ARG2 ...)':  If the split is a list, and the
> |      first element is `:', then the second element will be called as a
> |      function with ARGS given as arguments.  The function should return
> |      a SPLIT.
> | 
> |      For instance, the following function could be used to split based
> |      on the body of the messages:
> | 
> |           (defun split-on-body ()
> |             (save-excursion
> |               (set-buffer " *nnmail incoming*")
> |               (goto-char (point-min))
> |               (when (re-search-forward "Some.*string" nil t)
> |                 "string.group")))
> | 
> |      The `" *nnmail incoming*"' is narrowed to the message in question
> |      when the `:' function is run.
> \----
> 
> Is this enough?

Yes, except could you explain the wording for me?

when it says:

"The `" *nnmail incoming*"' is narrowed to the message in question
 when the `:' function is run."

Does this mean that if I (widen), i could potentially get other
messages?  In other words, is there a buffer that contains the
contents of the incoming spool file, which is then narrowed to each
message in turn?

I need to be able to narrow to the body of the message, the headers or
both.

Is it possible (for example) to narrow to the body of the already
narrowed region, and somehow widen to the previously narrowed region?
something like pop-narrow? :)

Thanks,

-- 
Josh Huber