Gnus development mailing list
 help / color / mirror / Atom feed
From: gsstark@MIT.EDU (Greg Stark)
Subject: Re: Sparse threads
Date: 19 Jan 1996 08:15:22 -0500	[thread overview]
Message-ID: <ycqybr4wck5.fsf@fierce-bad-rabbit.MIT.EDU> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 11 Jan 1996 22:25:24 +0100


sparse threads are really cool, thanks a lot lars!
i have two questions though:

the scenario is; i'm reading a response to an article that i've already read
another response to some other day does it show me that other response?  
in other words, having already read articles 1 and 2 in the following thread, 
i am now looking at article 3:
  [1] - [2]
    \ - [3]
i believe with a setting of t (equivalent of 'some) it will show me [1] but
not [2], the old reply.  in other words, sparse threads will get me:
  [1] - [3]
i think it is relatively important to know that i've already seen a reply. 
i would like a way of seeing such a reply without necessarily asking for the
entire thread since the beginning of time; there are several newsgroups where
threads are starting to march off past the width of my screen (and I decrease
the indentation already).


the other scenario is in my mail groups. a lot of the mail in my mail box
consists of replies to mail i sent out.  the mail i sent out isn't in my mail
box of course, but it is (now) stored in the mail archive.  it would be nice
if gnus would check for any missing article msg-id's in the outgoing mail (and
maybe news) archive.  This would actually make sparse threads useful in mail
groups; currently all it does is make a lot of pieces of mail take two lines,
one of which is mostly content-free.


greg


  reply	other threads:[~1996-01-19 13:15 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-01-08 12:08 Lars Magne Ingebrigtsen
1996-01-10 18:41 ` Per Abrahamsen
1996-01-11 21:25   ` Lars Magne Ingebrigtsen
1996-01-19 13:15     ` Greg Stark [this message]
1996-01-20  5:25       ` Lars Magne Ingebrigtsen
1996-01-20 14:09         ` Greg Stark
1996-01-20 22:07           ` d. hall
1996-01-22  2:51             ` Lars Magne Ingebrigtsen
1996-01-22  2:51           ` 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=ycqybr4wck5.fsf@fierce-bad-rabbit.MIT.EDU \
    --to=gsstark@mit.edu \
    /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).