Gnus development mailing list
 help / color / mirror / Atom feed
From: Karl Eichwalder <keichwa@gmx.net>
Subject: Re: gnus-large-newsgroup not respected
Date: 08 Mar 2001 18:35:41 +0100	[thread overview]
Message-ID: <shsnkoduz6.fsf@tux.gnu.franken.de> (raw)
In-Reply-To: <shk862d67n.fsf@tux.gnu.franken.de> (Karl Eichwalder's message of "06 Mar 2001 20:53:48 +0100")

Karl Eichwalder <keichwa@gmx.net> writes:

> Karl Eichwalder <keichwa@gmx.net> writes:
> 
> > The variable 'gnus-large-newsgroup' (default: 200) isn't respected
> > anymore.  Gnus will fetch _all_ unread article if I enter a "big" group
> > with 'gnus-group-select-group'.  'C-u 200 SPC' will offer old (read)
> > articles, too.

> Additonal info: It works for some gorups as said in the manual.

I fear I'll have to go back to 5.8.x.

There another behaviour that bugs me a lot.  I'm using INN and my expire
time is high (3 months for some groups).  Sometimes I'm reading a group
in a random fashion; often I cache an article, other articles I leave
unread and others are read.  Now it happens that Gnus decides to display
_all_ article of a large group and Gnus marks all articles 'til the most
recent cached article as read (often several hundreds...).

Has someone else observed such a behaviour?  Any proposal how to debug
this situation?

-- 
work : ke@suse.de                          |                   ,__o
     : http://www.suse.de/~ke/             |                 _-\_<,
home : keichwa@gmx.net                     |                (*)/'(*)


      reply	other threads:[~2001-03-08 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-06 19:45 Karl Eichwalder
2001-03-06 19:53 ` Karl Eichwalder
2001-03-08 17:35   ` Karl Eichwalder [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=shsnkoduz6.fsf@tux.gnu.franken.de \
    --to=keichwa@gmx.net \
    /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).