From: Christopher Culver <crculver@christopherculver.com>
To: ding@gnus.org
Subject: Re: Hooks for moving an article and for setting it expirable
Date: Mon, 18 Aug 2014 18:27:17 +0300 [thread overview]
Message-ID: <87r40dhl7u.fsf@aura.christopherculver.com> (raw)
In-Reply-To: <87mwb1lvrz.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Actually the data argument should be all you need. It will contain
> several of the important email headers from the message, if that's good
> enough, and that it isn't good enough, it also contains the article
> number, which is all you need to retrieve the whole article.
OK, that’s good. I’ve already written quite a bit of a function to do
what I need, assuming that I can get the article number and then
retrieve the raw article with that information.
The problem now is that I have no idea what type gnus-data-header
returns. Emacs' describe-function is not helpful. Is it a string
equivalent to the header portion of the maildir file? Is it a key-values
list, and if so, what the keys?
It’s strange that a lot of these features of gnus, though they are
useful for extending it, are not documented at all. Once I get my own
extension working correctly, I hope that a patch to provide a bare
minimum of documentation on these variables and functions will be
accepted.
Christopher Culver
next prev parent reply other threads:[~2014-08-18 15:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 16:26 Christopher Culver
2014-08-07 20:45 ` Adam Sjøgren
2014-08-08 1:59 ` Eric Abrahamsen
2014-08-17 20:10 ` Christopher Culver
2014-08-18 0:03 ` Eric Abrahamsen
2014-08-18 13:47 ` Christopher Culver
2014-08-18 14:25 ` Eric Abrahamsen
2014-08-18 15:27 ` Christopher Culver [this message]
2014-08-18 17:16 ` Christopher Culver
2014-08-19 1:16 ` Eric Abrahamsen
2014-08-20 18:16 ` Christopher Culver
2014-08-24 3:22 ` Eric Abrahamsen
2014-08-26 23:50 ` Christopher Culver
2014-08-27 2:07 ` Eric Abrahamsen
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=87r40dhl7u.fsf@aura.christopherculver.com \
--to=crculver@christopherculver.com \
--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).