From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: Re: accessing article information
Date: Tue, 19 Jul 2011 20:24:17 +0200 [thread overview]
Message-ID: <871uxmnn72.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <m38vrutfd9.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Tue, 19 Jul 2011 18:16:50 +0200")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> lee <lee@yun.yagibdah.de> writes:
>
>> how do you access information about an article from within a
>> `gnus-user-format-function-*' called when generating the summary buffer?
>> The documentation says:
>>
>> ,---- [ info (gnus) Summary Buffer Lines ]
>> | `u'
>> | User defined specifier. The next character in the format string
>> | should be a letter. Gnus will call the function
>> | `gnus-user-format-function-X', where X is the letter following
>> | `%u'. The function will be passed the current header as argument.
>> | The function should return a string, which will be inserted into
>> | the summary just like information from any other summary specifier.
>> `----
>>
>> What does the header passed to the function look like?
>
> It's a header vector. Use `mail-header-number' etc to access the slots.
Thanks! When I look at the macros defined in nnheader.el, there don't
seem to be any macros to access the marks an article has. Can I use
`gnus-summary-article-mark' as defined in gnus-sum.el in a
`gnus-user-format-function-*' to find out the marks?
Hm, looking at the .marks files, where does gnus store marks like
killed, caught up with, etc.?
next prev parent reply other threads:[~2011-07-19 18:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-06 8:17 lee
2011-07-19 16:16 ` Lars Magne Ingebrigtsen
2011-07-19 18:24 ` lee [this message]
2011-07-19 18:27 ` Lars Magne Ingebrigtsen
2011-07-19 22:50 ` lee
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=871uxmnn72.fsf@yun.yagibdah.de \
--to=lee@yun.yagibdah.de \
--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).