From: me@romanlagunov.ru (Roman Lagunov)
Subject: Re: reading nntp
Date: Sun, 01 Oct 2006 12:26:58 +0600 [thread overview]
Message-ID: <87hcyo5z65.fsf@romanlagunov.ru> (raw)
In-Reply-To: <m3hcyqfhyw.fsf@localhost.localdomain>
Gary Wessle <phddas@yahoo.com> writes:
> Hi
> I am running v5.9.0, in the Group buffer then I place the pointer over
> an item and hit <RET>, the mini buffer gives me the option weather to
> accept the (default 2395) which I then either hit <RET> or type in a
> number say 300 <RET>, but in either selection it takes the same amount
> of download (nntp read: 680K).
> is it not suppose to take less time for 300 than the default of 2395?
>
> here is my gnus.el
> ****************************************************************
> (setq gnus-select-method '(nntp "news.iprimus.com.au"))
> (setq gnus-check-new-newsgroups nil) ;save time at startup
> (setq gnus-fetch-old-headers 'some) ;prevents teared threads
Your problem is this line. Let's see:
,----C-h v gnus-fetch-old-headers
| gnus-fetch-old-headers's value is nil
|
| 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.
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ Look at here.
| You can customize this variable.
|
| Defined in `gnus-sum'.
`----
> (setq gnus-posting-styles
> '((".*"
> (name "Gary Wessle")
> (address "phddas@yahoo.com"))))
> (setq gnus-extract-address-components
> 'mail-extract-address-components)
> ****************************************************************
>
> thanks
--
Roman
prev parent reply other threads:[~2006-10-01 6:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-29 22:03 Gary Wessle
2006-10-01 6:26 ` Roman Lagunov [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=87hcyo5z65.fsf@romanlagunov.ru \
--to=me@romanlagunov.ru \
/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).