From: Ted Zlatanov <tzz@lifelogs.com>
Cc: ding@gnus.org
Subject: Re: new backend?
Date: Fri, 06 Dec 2002 15:21:35 -0500 [thread overview]
Message-ID: <4nadjiaofk.fsf@brainy.bwh.harvard.edu> (raw)
In-Reply-To: <84wumm7wi9.fsf@lucy.cs.uni-dortmund.de> (kai.grossjohann@uni-duisburg.de's message of "Fri, 06 Dec 2002 20:55:26 +0100")
On Fri, 06 Dec 2002, kai.grossjohann@uni-duisburg.de wrote:
> I've been thinking that it might be nice to allow for dynamic
> creation of digests in a group. You process-mark some articles, hit
> a button, and lo! you get a new article which is a digest of the
> process-marked ones which are then deleted.
>
> Later on, you add an article to such a digest.
>
> Digests can easily be viewed with C-d, so I think that would be a
> nifty thing to have.
Definitely.
> Not that it solves Jan's problems, of course.
I'll let Jan tell us, but I think that digest messages would be
exactly the right solution in this case. Baing able to access these
digests by name as external move/copy targets would pretty much do the
"bundle" functionality. I like it.
Ted
prev parent reply other threads:[~2002-12-06 20:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m28yz4xu8u.fsf@tnuctip.rychter.com>
2002-12-05 18:55 ` Ted Zlatanov
[not found] ` <m2smxcvyzo.fsf@tnuctip.rychter.com>
2002-12-06 13:33 ` Kai Großjohann
2002-12-06 19:21 ` Ted Zlatanov
2002-12-06 19:55 ` Kai Großjohann
2002-12-06 20:21 ` Ted Zlatanov [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=4nadjiaofk.fsf@brainy.bwh.harvard.edu \
--to=tzz@lifelogs.com \
--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).