Utter frustration

Utter frustration

[Hrvoje Niksic]

I cannot believe this is happening.

I'm seriously considering moving to slrn.  Or tin.  Or PINE.  Or
anything that would stop the pain.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Suburbia is where the developer bulldozes out the trees, then names
the streets after them.                              -- Bill Vaughn

Re: Utter frustration

[Alan Shutko]

>>>>> "H" == Hrvoje Niksic <hniksic@srce.hr> writes:

H> I cannot believe this is happening.  I'm seriously considering
H> moving to slrn.  Or tin.  Or PINE.  Or anything that would stop the
H> pain.

Sure, that would help.  You'd still have to edit the newsrc for those.

So, try this.  Make gnus write out a .newsrc as well as a .eld.  Edit
the .newsrc (easy with a quick macro and M-x apply).  Restart gnus.
Gnus should read both, with the article numbers in the .newsrc taking
precedence (because it's newer).  

-- 
Alan Shutko <ats@acm.org> - By consent of the corrupted
Never argue with a fool -- people might not be able to tell the difference.

Re: Utter frustration

[Jan Vroonhof]

Hrvoje Niksic <hniksic@srce.hr> writes:

> I'm seriously considering moving to slrn.  Or tin.  Or PINE.  Or
> anything that would stop the pain.

None of them would have helped. The problem remains the same.

You'll just have to M-x gnus-group-clear-data-on-native-groups RET and
be done with it.

Jan

Re: Utter frustration

[Per Abrahamsen]

Jan Vroonhof <vroonhof@math.ethz.ch> writes:

> Hrvoje Niksic <hniksic@srce.hr> writes:
> 
> > I'm seriously considering moving to slrn.  Or tin.  Or PINE.  Or
> > anything that would stop the pain.
> 
> None of them would have helped. The problem remains the same.

Gnus could be more helpful.  Something like:

(when (< last-article-number-on-server last-read-article-number)
  (if (yes-or-no-p "Server numbers have been reset, start on a fresh? ")
      (gnus-group-clear-data)
    (error "Server reset")))

I believe rn did that.

Re: Utter frustration

[Hrvoje Niksic]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Jan Vroonhof <vroonhof@math.ethz.ch> writes:
> 
> > Hrvoje Niksic <hniksic@srce.hr> writes:
> > 
> > > I'm seriously considering moving to slrn.  Or tin.  Or PINE.  Or
> > > anything that would stop the pain.
> > 
> > None of them would have helped. The problem remains the same.
> 
> Gnus could be more helpful.  Something like:
> 
> (when (< last-article-number-on-server last-read-article-number)
>   (if (yes-or-no-p "Server numbers have been reset, start on a fresh? ")
>       (gnus-group-clear-data)
>     (error "Server reset")))
> 
> I believe rn did that.

Yes, that would be very cool.  It would at least spare me the agony of 
trying to edit .newsrc.eld, .newsrc, `G E' output, and finding about
`gnus-group-clear-data' and `gnus-group-clear-data-on-native-groups',
in no particular order.

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Nostalgia isn't what it used to be.

Re: Utter frustration

[Lars Magne Ingebrigtsen]

Per Abrahamsen <abraham@dina.kvl.dk> writes:

> Gnus could be more helpful.  Something like:
> 
> (when (< last-article-number-on-server last-read-article-number)

The problem here is that `last-article-number-on-server' is something
that may not be all that reliable.  For instance, I sometimes switch
between having `gnus-read-active-file' set to t, `some' and nil.  On
the nntp server I use, all these three return differing data.
(Vaguely differing.)  So this test would routinely trigger for me.

Being asked to nuke all the data in this situation would not be
helpful, since many people always answer "yes" to questions they do
not ask.  And that would be disasterous in this situation.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen

Re: Utter frustration

[Christopher Davis]

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/>

Re: Utter frustration

[Lars Magne Ingebrigtsen]

Christopher Davis <ckd@ckdhr.com> writes:

> 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...

I don't like fudge, especially when the results may be unpredictable.

-- 
(domestic pets only, the antidote for overdose, milk.)
  larsi@gnus.org * Lars Magne Ingebrigtsen