From: Harry Putnam <reader@newsguy.com>
Subject: Re: Adulterate summary lines
Date: Mon, 16 Aug 2004 20:14:07 -0500 [thread overview]
Message-ID: <m3isbibm74.fsf@newsguy.com> (raw)
In-Reply-To: <m2oelb5bxi.fsf@c-ed5372d5.036-4-67626721.cust.bredbandsbolaget.se>
Jonas Steverud <tvrud@bredband.net> writes:
> I leave to others to interpret if that makes any sense or not. :-)
>
>> Using this option how would one make the Keywords line appear in
>> summary buffer or maybe the Date: line?
>
> Let the gnus-user-format-function-x above return what you want to add
> as a string.
Well, first I can't even begin to see what on earth it does. Or I
mean how it does this. How can you tell this function which string to
return for example?
I don't see the stuff you posted as a result of your function. What I
see is a summary buffer that looks like:
? [ 59: test] Adulterate summary lines
RA [ 90: test]
R [ 28: test] Gnus for information storage (Was: Adulterate summary lines)
Line one is my post, line 2 is your answer and line 3 is another
message from you about using gnus as info storage tool.
I have not the slightest clue how or what is coding this.
It would be handy if you provided some notes as to what is doing what.
(defun gnus-user-format-function-x (STR)
(message (prin1-to-string STR))
"test")
The only part I actuall sort of see is that "test" being a string in
double quotes was returned.
As I posted to start the manual says "function would be passed the
current header"
What header is being passed?
But before I say any more I'm going to research the stuff you suggested.
next prev parent reply other threads:[~2004-08-17 1:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 11:12 Harry Putnam
2004-08-16 15:40 ` Jonas Steverud
2004-08-17 0:15 ` Harry Putnam
2004-08-17 1:14 ` Harry Putnam [this message]
2004-08-17 7:41 ` Jonas Steverud
2004-08-17 11:29 ` Harry Putnam
2004-08-16 15:52 ` Gnus for information storage (Was: Adulterate summary lines) Robert Epprecht
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=m3isbibm74.fsf@newsguy.com \
--to=reader@newsguy.com \
/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).