From: Burton Samograd <burton@samograd.ca>
To: ding@gnus.org
Subject: Re: Possible bugs (gnus-demon and switching modes when composing messages)
Date: Thu, 22 Nov 2012 08:20:34 -0700 [thread overview]
Message-ID: <87k3tdacl9.fsf@samograd.ca> (raw)
In-Reply-To: <877gpejipj.fsf@riseup.net>
Sergio Durigan Junior <sergiodj@riseup.net> writes:
> On Wednesday, November 21 2012, I wrote:
>
>> On Wednesday, November 21 2012, Matt Ford wrote:
>>
>>> It might. To be clear when setting 'consider-all-articles' to 't', when
>>> using nntp groups it produced unwanted behaviour. Every time I went to
>>> a newsgroup it downloaded every single article ever posted every time
>>> (regardless if I'd all ready done so). And some newsgroups are big.
>>
>> Ah, ok, I know what you mean now. `gnus-agent-consider-all-articles'
>> is 'nil' for me since the beginning, and I didn't change it. So I think
>> this is not the problem...
>
> Well, after more research on that topic, I found this:
>
> http://comments.gmane.org/gmane.discuss/11608
>
> In short: the author of the thread was complaining more or less about
> the same thing, and his problem was that he was using
> `gnus-fetch-old-headers', setting it to `t'.
>
> I do the same thing here in .gnus, and then I started to do some
> experiments. Now, Gnus opens the newsgroup much faster, of course. It
> doesn't have to download everything from news.gmane.org, only some
> messages (I set `gnus-fetch-old-headers' to 500 specifically on gmane
> groups).
>
> So, my question now is: what do you guys use? Do you also use
> `gnus-fetch-old-headers'?
I use gnus-fetch-old-headers, but I also use a leafnode as a local nntp
server. This gives much better response when fetching a the larger
number of articles that fetch old headers requires. It is pretty easy to
setup to fetch articles from a number of remote nttp servers.
--
Burton Samgorad
next prev parent reply other threads:[~2012-11-22 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-06 21:39 Sergio Durigan Junior
2012-10-07 18:39 ` Tassilo Horn
2012-10-14 6:40 ` Sergio Durigan Junior
2012-10-14 10:28 ` Tassilo Horn
2012-11-15 5:52 ` Sergio Durigan Junior
2012-11-15 9:20 ` Matt Ford
2012-11-21 4:06 ` Sergio Durigan Junior
2012-11-21 10:49 ` Matt Ford
2012-11-21 22:01 ` Sergio Durigan Junior
2012-11-22 5:43 ` Sergio Durigan Junior
2012-11-22 7:12 ` Eric Abrahamsen
2012-11-23 2:56 ` Sergio Durigan Junior
2012-11-22 15:20 ` Burton Samograd [this message]
2012-11-25 5:10 ` Sergio Durigan Junior
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=87k3tdacl9.fsf@samograd.ca \
--to=burton@samograd.ca \
--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).