Gnus development mailing list
 help / color / mirror / Atom feed
From: Gabe Logan <session13@poczta.fm>
To: ding@gnus.org
Subject: Re: Gnus always fetching all messages from nntp server
Date: Sun, 21 Nov 2010 11:30:29 +0100	[thread overview]
Message-ID: <87r5efm0je.fsf@seashell.home> (raw)
In-Reply-To: <m3vd3rm8j0.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Gabe Logan <session13@poczta.fm> writes:
>
>> Thanks, I've unset gnus-fetch-old-headers and now it fetches only unread
>> messages. But when gnus-fetch-old-headers is t, shouldn't Gnus fetch
>> only those old headers which belongs to unread messages ? 
>
> I'm not sure what you mean.  If you don't have `gnus-fetch-old-headers'
> set, it fetches only the headers for the articles you request (which is
> normally the unread articles).  If you have it set, it fetches all headers.

I'll try to make it clear. I wanted Gnus to make A T command on every
unread article when entering group buffer. This way, when I have no
unread articles, Gnus won't fetch any headers from server. But if
someone will post to a old thread, Gnus will show this message in my
buffer along with all predecesing posts in this thread. The time Gnus
will spend on fetching messages for one or few threads should be much
smaller then when fetching all 80.000+ messages available on server.

Now, when I discovered the A T command I don't really think that the
described above functionality is necessery. Someone who reads his news
every day doesn't need to go through the whole thread every time he gets
new message (no time wasted on fetching old msgs). And in case of need
he can use A T to see whole thread.

-- 
Thanks
Gabe




  reply	other threads:[~2010-11-21 10:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-20  9:01 Gabe Logan
2010-11-21  4:26 ` Lars Magne Ingebrigtsen
2010-11-21  7:32   ` Gabe Logan
2010-11-21  7:37     ` Lars Magne Ingebrigtsen
2010-11-21 10:30       ` Gabe Logan [this message]
2010-11-21 18:14         ` Lars Magne Ingebrigtsen
2010-11-22  6:15           ` Gabe Logan
2010-11-22  6:41           ` Russ Allbery
2010-11-24 21:15             ` Lars Magne Ingebrigtsen
2010-11-24 21:22               ` Russ Allbery
2010-11-25 10:44               ` Steinar Bang
2010-11-25 14:27                 ` 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=87r5efm0je.fsf@seashell.home \
    --to=session13@poczta.fm \
    --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).