From: abraham@dina.kvl.dk (Per Abrahamsen)
Subject: Re: enter-digest-group'ing
Date: 29 Feb 1996 19:20:33 +0100 [thread overview]
Message-ID: <rjivgqc7ta.fsf@ssv4.dina.kvl.dk> (raw)
In-Reply-To: jvinson@cheux.ecs.umass.edu's message of 29 Feb 1996 09:18:41 -0500
>>>>> "JV" == Jack Vinson <jvinson@cheux.ecs.umass.edu> writes:
JV> Why can't mail digests be broken into their component articles and then
JV> treated as such? RMail has a feature that splits the digest into
JV> individual messages and wipes the digest. For mailing list, this seems
JV> like it would be the best way to go. It would let us refer to an article
JV> directly and possibly see how it fits into a thread.
You can do this with the following three commands:
C-d split into digest
M p a mark all articles
B c group RET copy digested articles to `group'
It would be convenient with a function that would do this
automatically, especially if you could put such a function in the kill
file for digested groups like `comp.risk'.
E.g. comp.risk.KILL:
(gnus-split "nnml:comp.risk.undigestified")
(gnus-expunge "U")
next prev parent reply other threads:[~1996-02-29 18:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-02-27 22:12 Selected articles, replying vs. forwarding Andy Eskilsson
1996-02-28 6:59 ` Lars Magne Ingebrigtsen
1996-02-28 7:57 ` Selected articles, replying vs. enter-digest-group'ing Greg Stark
1996-02-29 8:57 ` Lars Magne Ingebrigtsen
1996-02-29 14:18 ` enter-digest-group'ing Jack Vinson
1996-02-29 17:32 ` enter-digest-group'ing Joe Hildebrand
1996-02-29 18:20 ` Per Abrahamsen [this message]
1996-02-28 20:11 ` Selected articles, replying vs. forwarding Edward J. Sabol
1996-02-28 20:51 ` Steve Baumgarten
1996-02-29 8:58 ` Lars Magne Ingebrigtsen
1996-02-29 8:58 ` 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=rjivgqc7ta.fsf@ssv4.dina.kvl.dk \
--to=abraham@dina.kvl.dk \
/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).