From: Nelson Ferreira <nelson.ferreira@ieee.org>
Subject: Re: ? instead of R as default
Date: Fri, 05 May 2006 01:12:26 -0400 [thread overview]
Message-ID: <m3wtd1xdfp.fsf@tuxie.homelinux.net> (raw)
In-Reply-To: <87zmhx5b36.fsf@gmail.com>
"Fredrik" == Fredrik Bulow <kaliumfredrik@gmail.com> writes:
Fredrik> Hi all!
Fredrik> When there are new posts under a certain thread I wan to see all old
Fredrik> articles in that thread by default. What is the best way to achieve
Fredrik> this?
I use the following. I started with some, but for deep threads it
impacted performance of group entering, so now I allow upto 40 old
articles to be fetched to complete the threads.
,----[ C-h v gnus-fetch-old-headers RET ]
| `gnus-fetch-old-headers' is a variable declared in Lisp.
| -- loaded from "gnus-sum"
|
| Value: 40
|
| Documentation:
| *Non-nil means that Gnus will try to build threads by grabbing old headers.
| If an unread article in the group refers to an older, already
| read (or just marked as read) article, the old article will not
| normally be displayed in the Summary buffer. If this variable is
| t, Gnus will attempt to grab the headers to the old articles, and
| thereby build complete threads. If it has the value `some', all
| old headers will be fetched but only enough headers to connect
| otherwise loose threads will be displayed. This variable can
| also be a number. In that case, no more than that number of old
| headers will be fetched. If it has the value `invisible', all
| old headers will be fetched, but none will be displayed.
|
| The server has to support NOV for any of this to work.
|
| This feature can seriously impact performance it ignores all
| locally cached header entries.
`----
[...]
--
Nelson Ferreira
next prev parent reply other threads:[~2006-05-05 5:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 4:50 Fredrik Bulow
2006-05-05 5:12 ` Nelson Ferreira [this message]
2006-05-05 7:34 ` Leon
[not found] ` <mailman.1467.1146814513.9609.info-gnus-english@gnu.org>
2006-05-06 4:36 ` Fredrik Bulow
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=m3wtd1xdfp.fsf@tuxie.homelinux.net \
--to=nelson.ferreira@ieee.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).