From: Lars Ingebrigtsen <larsi@gnus.org>
To: ding@gnus.org
Subject: Re: Automatically processing plain text attachments
Date: Wed, 26 Jan 2011 16:53:14 -0800 [thread overview]
Message-ID: <8739of9ngl.fsf@gnus.org> (raw)
In-Reply-To: <87vd1cew6o.fsf@berkeley.edu>
Richard Lawrence <richard.lawrence@berkeley.edu> writes:
> 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?
Yes, I think so.
> 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?
Yes, that's a much more controlled situation. There's a bazillion
article mode hooks/functions you can use, depending on what's most
convenient.
> 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?
I'd suggest looking at the manual for what hook to use, and then look at
the code.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2011-01-27 0:53 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
2011-01-27 0:53 ` Lars Ingebrigtsen [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=8739of9ngl.fsf@gnus.org \
--to=larsi@gnus.org \
--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).