Gnus development mailing list
 help / color / mirror / Atom feed
From: Joe Hildebrand <hildjj@fuentez.com>
Subject: Re: enter-digest-group'ing
Date: 29 Feb 1996 10:32:48 -0700	[thread overview]
Message-ID: <yya20ne11hb.fsf@arls2006.fuentez.com> (raw)
In-Reply-To: jvinson@cheux.ecs.umass.edu's message of 29 Feb 1996 09:18:41 -0500

> "Jack" == Jack Vinson <jvinson@cheux.ecs.umass.edu> writes:

   Jack> Why can't mail digests be broken into their component
   Jack> articles and then treated as such?  RMail has a feature that
   Jack> splits the digest into individual messages and wipes the
   Jack> digest.  For mailing list, this seems like it would be the
   Jack> best way to go.  It would let us refer to an article directly
   Jack> and possibly see how it fits into a thread.

cool.  make it also work in nntp groups, putting the exploded articles
into the cache.  that way, reading comp.risks would be a lot threadier.

-- 
Joe Hildebrand                  Fuentez Systems Concepts
hildjj@fuentez.com              11781 Lee-Jackson Hwy, Suite 700
Lead Software Engineer          Fairfax, VA 22033
	"Breakfast recapitulates phylogeny" - Spider Robinson


  reply	other threads:[~1996-02-29 17:32 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         ` Joe Hildebrand [this message]
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=yya20ne11hb.fsf@arls2006.fuentez.com \
    --to=hildjj@fuentez.com \
    /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).