Gnus development mailing list
 help / color / mirror / Atom feed
From: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Sparse threads
Date: 11 Jan 1996 22:25:24 +0100	[thread overview]
Message-ID: <ivii4e62.fsf@bjob.no> (raw)
In-Reply-To: Per Abrahamsen's message of Wed, 10 Jan 1996 19:41:52 +0100
In-Reply-To: Per Abrahamsen's message of Wed, 10 Jan 1996 19:52:59 +0100

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> I hope it works with the various values of `gnus-fetch-old-headers',
> in particular (setq gnus-fetch-old-headers 'some) should give you all
> the same articles as trn finds.

Yes, sparse threads should work very nicely with
`gnus-fetch-old-headers' set to `some', I think.  

Oh, I forgot to mention that there are three settings to
`gnus-build-sparse-threads' -- nil, t, and `total', which is kinda
like nil, `some' and t for `gnus-fetch-old-headers'.  Perhaps I should
use the same naming scheme for both variables?  Yes, I think so.  

I haven't road-tested it much, but these sparse threads seem quite
pleasing to me.  They do make many threads quite a lot deeper,
though. 

-- 
   Lars Magne Ingebrigtsen * larsi@ifi.uio.no
      (a red leaf that falls from the purple tree)


  reply	other threads:[~1996-01-11 21:25 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 [this message]
1996-01-19 13:15     ` Greg Stark
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=ivii4e62.fsf@bjob.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).