Gnus development mailing list
 help / color / mirror / Atom feed
From: larsi@ifi.uio.no (Lars Magne Ingebrigtsen)
Subject: Re: Selected articles, replying vs. enter-digest-group'ing
Date: 29 Feb 1996 08:57:56 +0000	[thread overview]
Message-ID: <w8sravecxuz.fsf_-_@eistla.ifi.uio.no> (raw)
In-Reply-To: gsstark@MIT.EDU's message of 28 Feb 1996 02:57:15 -0500

gsstark@MIT.EDU (Greg Stark) writes:

> It would be really cool if enter-digest-group respected the process mark.
> This would involve adding features to nndoc, but would be great with those
> multi-part FAQs and digests like Risks that have threads that span multiple
> digests.  

This is basically the "nnmultidoc" backend that I've been mulling over
for, uhm, years.

But perhaps one could just use virtual groups instead?  Each digest is
opened as a nndoc group, and then an nnvirtual group is created using
these nndoc groups are component groups?  That should work.

I've now added this to the Red Gnus todo list.

-- 
  "Yes.  The journey through the human heart 
     would have to wait until some other time."


  reply	other threads:[~1996-02-29  8:57 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 [this message]
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         ` enter-digest-group'ing Per Abrahamsen
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=w8sravecxuz.fsf_-_@eistla.ifi.uio.no \
    --to=larsi@ifi.uio.no \
    /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).