From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: WIBNI - enhanced limiting
Date: Fri, 17 Aug 2001 19:12:12 +0200 [thread overview]
Message-ID: <m3pu9uwqz7.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <m1snevn6sy.fsf@reader.newsguy.com>
Harry Putnam <reader@newsguy.com> writes:
> C-u Date / x Keywords <RET> WORD <RET> - would generate a summary
> Where the Date/Subject headers would be displayed for those same messages.
>
> I hope someone answers with:
> Oh, you mean like the stuff Committed to CVS yesterday?
I'm afraid not.
This would, like, require altering `gnus-summary-line-format' to
include the extra header when regenerating the summary buffer after
`/ x'-ing. And in a somewhat complicated fashion, right? It sounds
kinda fiddly...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2001-08-17 17:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 18:40 Harry Putnam
2001-08-17 17:12 ` 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=m3pu9uwqz7.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).