From: Charles Philip Chan <cpchan@bell.net>
To: ding@gnus.org
Subject: Re: Showing threads with IMAP
Date: Thu, 24 Jul 2014 10:19:53 -0400 [thread overview]
Message-ID: <87zjfyon3q.fsf@karnak.MagnumOpus.khem> (raw)
In-Reply-To: <m11ttahn2o.fsf@pdavismbp15.iscinternal.com>
[-- Attachment #1: Type: text/plain, Size: 979 bytes --]
Peter Davis <pfd@pfdstudio.com> writes:
> Thanks for all the help and suggestions, everyone. Setting
> gnus-build-sparse-threads to t does seem to do what I was looking for,
> but now opening a group takes too long. So I think I'll drop back to
> *not* showing previously read messages in the thread, and using 'A T'
> when I want to see the history.
Change the value to "some". It is much quicker:
,----
| gnus-build-sparse-threads is a variable defined in `gnus-sum.el'.
| Its value is some
| Original value was nil
|
| Documentation:
| *If non-nil, fill in the gaps in threads.
| If `some', only fill in the gaps that are needed to tie loose threads
| together. If `more', fill in all leaf nodes that Gnus can find. If
| non-nil and non-`some', fill in all gaps that Gnus manages to guess
`----
Charles
--
"Are [Linux users] lemmings collectively jumping off of the cliff of
reliable, well-engineered commercial software?"
(By Matt Welsh)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
prev parent reply other threads:[~2014-07-24 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-22 20:01 Peter Davis
2014-07-22 20:53 ` Steinar Bang
2014-07-22 20:56 ` Peter Davis
2014-07-23 1:01 ` Eric Abrahamsen
2014-07-23 12:37 ` Peter Davis
2014-07-23 14:37 ` Jorge A. Alfaro-Murillo
2014-07-23 14:45 ` Peter Davis
2014-07-24 0:50 ` Eric Abrahamsen
2014-07-24 14:02 ` Peter Davis
2014-07-24 14:19 ` Charles Philip Chan [this message]
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=87zjfyon3q.fsf@karnak.MagnumOpus.khem \
--to=cpchan@bell.net \
--cc=ding@gnus.org \
/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).