From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: Suggestion for a nicer summary buffer
Date: Wed, 22 Aug 2001 00:05:16 +0200 [thread overview]
Message-ID: <m34rr1ax2b.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <wv3zk86n.fsf@hschmi22.userfqdn.rz-online.de>
Frank Schmitt <Azzrael@rz-online.de> writes:
> 1) A new variable top-of-thread-line-format. This should be used to
> print the summary line which stands for a collapsed thread, so you could
> have infos about the thread there (number of articles, thread score...)
> When the thread is expanded it should be, redrawn using summary-line-format.
Hm... That's a pretty good idea, I think.
> I tried to do it on my own, but on 1) I can't even find the code where
> the line is drawn.
It's the `eval' in `gnus-summary-prepare-threads'. On line 4391.
(Wow. How long is that file, anyway? Oops. 10K lines.)
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2001-08-21 22:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-19 22:15 Frank Schmitt
2001-08-21 12:28 ` Frank Schmitt
2001-08-21 13:08 ` Kai Großjohann
2001-08-21 13:54 ` Frank Schmitt
2001-08-21 15:04 ` Kai Großjohann
2001-08-21 22:05 ` Lars Magne 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=m34rr1ax2b.fsf@quimbies.gnus.org \
--to=larsi@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).