Gnus development mailing list
 help / color / mirror / Atom feed
From: Richard Lawrence <richard.lawrence@berkeley.edu>
To: ding@gnus.org
Subject: Re: Automatically processing plain text attachments
Date: Tue, 25 Jan 2011 09:21:19 -0800	[thread overview]
Message-ID: <87vd1cew6o.fsf@berkeley.edu> (raw)
In-Reply-To: <87ei82otcm.fsf@gnus.org>

Lars Ingebrigtsen <larsi@gnus.org> writes:

> Richard Lawrence <richard.lawrence@berkeley.edu> writes:
>
>> Perhaps my question boils down to: what hooks are available in Gnus that
>> would allow me batch process the full content of these paper-submission
>> emails at the time they are split from my inbox (without having to
>> download the full content of *every* mail, e.g., by setting
>> nnimap-split-download-body)?
>
> Hm...  I don't think there's any easy way to hook that up.  The
> -download-body thing is done sort of "top level" before noticing what
> groups the articles are supposed to go to.

I guess it wouldn't be *too* big a deal to download the body of all
messages...I don't get that much mail, thanks to the combination of Gnus
and Gmane...

In that case, would I be able to do what I want by installing a function
as the second element of my split rule in nnimap-split-rule?  Would this
function be called in a buffer containing the entire message body?

Another option would be to do this semi-interactively, which may be what
I want anyway.  Is it easier to call a hook on a message when it is
*read*, rather than when it is split?

> The only this that occurs to me immediately is to look at the
> `nnmail-split-trace' variable after the split has finished.  If new
> messages has shown up in your special group, then do, er, stuff based on
> that.  For instance, request the new messages one by one, and run some
> filtering stuff...

Where would I look to learn how to do these things?  Is there a guide to
hacking somewhere?  Or should I just dive into the Gnus code?

> It's just a small matter of programming.  :-)

Indeed.  

Thanks for your help, Lars!

Richard




  reply	other threads:[~2011-01-25 17:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-24  3:11 Richard Lawrence
2011-01-24 22:00 ` Lars Ingebrigtsen
2011-01-25 17:21   ` Richard Lawrence [this message]
2011-01-27  0:53     ` Lars Ingebrigtsen

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=87vd1cew6o.fsf@berkeley.edu \
    --to=richard.lawrence@berkeley.edu \
    --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).