From: Christopher Davis <ckd@ckdhr.com>
Subject: Re: Utter frustration
Date: 29 Sep 1998 09:29:43 -0400 [thread overview]
Message-ID: <w467e7oxmg.fsf@loiosh.kei.com> (raw)
In-Reply-To: larsi@gnus.org's message of "23 Sep 98 20:14:29 GMT"
PA> == Per Abrahamsen <abraham@dina.kvl.dk>
LMI> == Lars Magne Ingebrigtsen <larsi@gnus.org>
PA> Gnus could be more helpful. Something like:
PA> (when (< last-article-number-on-server last-read-article-number)
LMI> The problem here is that `last-article-number-on-server' is
LMI> something that may not be all that reliable. For instance, I
LMI> sometimes switch between having `gnus-read-active-file' set to t,
LMI> `some' and nil. On the nntp server I use, all these three return
LMI> differing data. (Vaguely differing.) So this test would
LMI> routinely trigger for me.
Toss in a fudge factor, then. Very few resets are going to be less
than, say, 5000 articles or so, especially since we're in extremely late
September 1993...
"Vaguely differing" is probably <100, almost certainly <500, and almost
definitely <1000. 5000 is for extra extra safety.
(defcustom gnus-group-reset-fudge-factor 5000
"Fudge factor when checking for reset article numbers.
If the article number goes backwards more than this number, ask the
user whether to reset the group."
:group 'gnus-fixing-other-peoples-mistakes
:type 'integer)
Okay, so the :group is probably going to have to change...
--
Christopher Davis * <ckd-sig@ckdhr.com> * <URL:http://www.ckdhr.com/ckd/>
Put location information in your DNS! <URL:http://www.ckdhr.com/dns-loc/>
next prev parent reply other threads:[~1998-09-29 13:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-09-21 15:44 Hrvoje Niksic
1998-09-21 16:05 ` Alan Shutko
1998-09-21 16:07 ` Jan Vroonhof
1998-09-21 17:31 ` Per Abrahamsen
1998-09-21 17:43 ` Hrvoje Niksic
1998-09-23 20:14 ` Lars Magne Ingebrigtsen
1998-09-29 13:29 ` Christopher Davis [this message]
1998-10-01 3:10 ` 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=w467e7oxmg.fsf@loiosh.kei.com \
--to=ckd@ckdhr.com \
/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).