From: Kai Grossjohann <grossjohann@charly.informatik.uni-dortmund.de>
Subject: Groups within groups, or Digests++
Date: 01 Dec 1996 23:24:16 +0100 [thread overview]
Message-ID: <vafral9299r.fsf@ls6.informatik.uni-dortmund.de> (raw)
Yo!
I've been thinking (what a rare event :) and here's what I came up
with: I often keep old articles around in a group for some reason. If
there are several of those it makes the group large which in turn
slows down entering the group. Now there's this digests feature.
WIBNI one could just process-mark a number of articles and say "make
these a digest and put the digest in the current group"? This is
already possible using "S O m" and the Gcc header. But what if a new
message arrives some time later that I'd like to put in the digest,
too? Would it be hard to make something that lets me add messages to
a digest?
I think I'll have to investigate using dormant articles for this
(they're there but not displayed, so they don't slow down summary
generation), but I'm kind of afraid that I can't see 'em makes me
forget about 'em.
kai
--
I wonder why nobody don't like me,
or is it de fact dat I'm ugly? -- Harry Belafonte
next reply other threads:[~1996-12-01 22:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-12-01 22:24 Kai Grossjohann [this message]
1996-12-05 18:46 ` Lars Magne Ingebrigtsen
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=vafral9299r.fsf@ls6.informatik.uni-dortmund.de \
--to=grossjohann@charly.informatik.uni-dortmund.de \
/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).