Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Trying to enter a group: "registry max-hard size limit reached"
Date: Mon, 09 May 2011 15:03:32 -0500	[thread overview]
Message-ID: <87y62fbq0b.fsf@lifelogs.com> (raw)
In-Reply-To: <877h9zpsk7.fsf@member.fsf.org>

On Mon, 09 May 2011 21:44:40 +0200 Tassilo Horn <tassilo@member.fsf.org> wrote: 

TH> Ted Zlatanov <tzz@lifelogs.com> writes:
TZ> As Tassilo said, increase `gnus-registry-max-entries' until I fix
TZ> it to call `registry-prune'.  No need to remove the registry
TZ> (though that works too, certainly).
>> 
>> Now the code calls `registry-prune' but will still fail if the
>> registry is full.  I think that's the right thing to do, though I
>> could ask the user if he wants to increase
>> `gnus-registry-max-entries'.

TH> Why can it still be full after pruning?  IMO, if I set the registry size
TH> to be at maximum 1000 articles long, I'd expect it to work as a LRU
TH> cache...

Yes, but rather than losing the data the user may want to raise the hard
limit.  So we could be friendlier before `registry-prune' goes in.

Ted




  reply	other threads:[~2011-05-09 20:03 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-08 21:04 Adam Sjøgren
2011-05-09  6:37 ` Tassilo Horn
2011-05-09  8:47 ` Adam Sjøgren
2011-05-09 10:54   ` Ted Zlatanov
2011-05-09 15:41     ` Adam Sjøgren
2011-05-09 16:26       ` Ted Zlatanov
2011-05-09 16:50         ` Adam Sjøgren
2011-05-09 17:55           ` Ted Zlatanov
2011-05-10 10:29             ` Adam Sjøgren
2011-05-10 17:45               ` Ted Zlatanov
2011-05-09 17:52     ` Ted Zlatanov
2011-05-09 19:44       ` Tassilo Horn
2011-05-09 20:03         ` Ted Zlatanov [this message]
2011-05-10 10:29           ` Adam Sjøgren
2011-05-10 10:29       ` Adam Sjøgren

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=87y62fbq0b.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).