From: Alexander Baier <alexander.baier@mailbox.org>
To: ding@gnus.org
Subject: Re: function to access raw article
Date: Fri, 31 Oct 2014 12:43:14 +0100 [thread overview]
Message-ID: <87y4rwh3cd.fsf@mailbox.org> (raw)
In-Reply-To: <upzc8ujwpkka.fsf@dod.no> (Steinar Bang's message of "Fri, 31 Oct 2014 12:04:05 +0100")
On 2014-10-31 12:04 Steinar Bang wrote:
>>>>>> Alexander Baier <alexander.baier@mailbox.org>:
>
>> I have information in the body of the the article that I want to
>> display in the summary line.
>
> One problem with this, could be that some backends don't have the
> article body available at the time of rendering the summary buffer...?
> (I think this is the case for nntp, and possibly also nnimap...?)
The backend in question is nnmaildir, which should have access to the
articles body, as it is already locally available in my file
system. The gnus-summary-line-format is set as a group parameter on only
one group, so that it does not interfere with my normal summary line.
Maybe gnus does not expect me to call some article display commands
during the rendering of the summary buffer? Does anyone know any
specifics on this?
> I think the summary buffer uses what's available in what's returned by
> NNTP as NOV data:
> http://tools.ietf.org/html/rfc3977#section-8
Thank you for the pointer! Sadly this would not be enough for me. :(
Regards,
--
Alexander Baier
next prev parent reply other threads:[~2014-10-31 11:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-31 8:29 Alexander Baier
2014-10-31 8:53 ` Igor Sosa Mayor
2014-10-31 9:57 ` Alexander Baier
2014-10-31 11:04 ` Steinar Bang
2014-10-31 11:43 ` Alexander Baier [this message]
2014-10-31 11:45 ` Igor Sosa Mayor
2014-10-31 11:50 ` Alexander Baier
2014-10-31 14:19 ` Eric Abrahamsen
2014-10-31 15:18 ` Alexander Baier
2014-10-31 15:29 ` Eric Abrahamsen
2014-10-31 12:55 ` Ted Zlatanov
2014-10-31 13:38 ` Alexander Baier
2014-10-31 14:01 ` Alexander Baier
2014-10-31 14:22 ` Peter Münster
2014-10-31 15:20 ` Alexander Baier
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=87y4rwh3cd.fsf@mailbox.org \
--to=alexander.baier@mailbox.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).