From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: [Various] I'm starting this discussion (was "gnus-uu-digest-mail-forward (S-O-m) nit")
Date: 21 Apr 2000 01:29:02 +0200 [thread overview]
Message-ID: <m31z40tkqp.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <svsnwg8k2a.fsf@hodge.primus.com>
Steve Harris <sharris@primus.com> writes:
> Yeah, I noticed that. It's an unfortunate trade-off, because as a user
> I wouldn't have noticed that we're reusing the fragmented message
> collation routine to figure out which messages I'm referring to
> here. I can see how this sequence-based grouping is useful for
> uudecoding, but the basic "digest and forward" command doesn't
> necessarily have anything to do with fragmented messages. The naive
> user (me, in this case) suffers as a result of this code reuse.
Yes -- that command behaves the way it does for hysterical raisins.
(The command debuted as a part of gnus-uu.)
> So if I want to be able to digest and mail an entire sub-thread, is
> there some quick way to process-mark the sub-thread and get them all
> digested in the right order?
`T # S O m'.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2000-04-20 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-24 17:07 Steven Elliot Harris
2000-04-20 20:53 ` Lars Magne Ingebrigtsen
2000-04-20 22:49 ` Steve Harris
2000-04-20 23:29 ` Lars Magne Ingebrigtsen [this message]
2000-04-21 2:31 ` Steve Harris
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=m31z40tkqp.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).