Marks woes on upgrade from oort 0.03 -> 0.04.

Marks woes on upgrade from oort 0.03 -> 0.04.

[Karra]

On upgrading, I found that the read marks are all gone.  I believe I
read another report on this before.  But the wierdness does not end
there.  Let me explain:

(a) I installed 0.04 and started emacs.  I started gnus with M-x
    gnus-unpluged RET
(b) A gory sight greeted me --- a gazillion unread messages.
(c) I thought for a second and quickly pressed 'q' to quit from.
(d) After a few deep breaths, I did the M-x gnus-unplugged RET
    routine, and lo and behold!!  things were as they should have
    been.
(e) I repeated the above steps (from starting emacs) to confirm this
    behaviour.
(f) In one pass, during the second gnus invocation, I entered a group
    and changed some marks, 's'ed in *Group* buffer and quit emacs.
    Then I restarted Emacs.  Again all groups showed unread messages
    _except_ the group I had just edited.
(g) I restarted Emacs and did (setq nnml-marks-is-evil t) and life
    appeared normal.

Is there a fix for this in CVS?

-- 
"Have you ever fought an IDEA, Picard?"
      -- Gowron, Star Trek TNG.

Re: Marks woes on upgrade from oort 0.03 -> 0.04.

[Lars Magne Ingebrigtsen]

Karra <karra@cs.utah.edu> writes:

> (a) I installed 0.04 and started emacs.  I started gnus with M-x
>     gnus-unpluged RET
> (b) A gory sight greeted me --- a gazillion unread messages.
> (c) I thought for a second and quickly pressed 'q' to quit from.
> (d) After a few deep breaths, I did the M-x gnus-unplugged RET
>     routine, and lo and behold!!  things were as they should have
>     been.
> (e) I repeated the above steps (from starting emacs) to confirm this
>     behaviour.

So the first time you start Gnus within an Emacs session, all articles
in all nnml groups become unread?

> (g) I restarted Emacs and did (setq nnml-marks-is-evil t) and life
>     appeared normal.
>
> Is there a fix for this in CVS?

I'd suggest upgrading at least to 0.05 to see whether that helps.

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

Re: Marks woes on upgrade from oort 0.03 -> 0.04.

[Karra]

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> Karra <karra@cs.utah.edu> writes:
>
>> (a) I installed 0.04 and started emacs.  I started gnus with M-x
>>     gnus-unpluged RET
>> (b) A gory sight greeted me --- a gazillion unread messages.
>> (c) I thought for a second and quickly pressed 'q' to quit from.
>> (d) After a few deep breaths, I did the M-x gnus-unplugged RET
>>     routine, and lo and behold!!  things were as they should have
>>     been.
>> (e) I repeated the above steps (from starting emacs) to confirm this
>>     behaviour.
>
> So the first time you start Gnus within an Emacs session, all articles
> in all nnml groups become unread?
>
>> (g) I restarted Emacs and did (setq nnml-marks-is-evil t) and life
>>     appeared normal.
>>
>> Is there a fix for this in CVS?
>
> I'd suggest upgrading at least to 0.05 to see whether that helps.

I upgraded to latest CVS and tried again.  The problem, as stated,
persisted.  The actual problem turned out to be the presence of some
"wrong" .marks file that got generated sometime...  I deleted all
.marks files and restarted Gnus.  This solved the problem.  This
delete-the-marks-file-and-restart routine also worked with
oort-0.04...

How about inserting the following into the manual?

--- gnus.texi.old       Sun Jan 13 05:36:43 2002
+++ gnus.texi   Sun Jan 13 05:42:19 2002
@@ -13688,6 +13688,10 @@
 to restore the group (after restoring the backup into the nnml
 directory).

+If for some reason you believe your @file{.marks} files are screwed
+up, you can just delete them all.  Gnus will then correctly regenerate
+them next time it starts.
+
 Virtual server settings:

 @table @code


-- 
"Have you ever fought an IDEA, Picard?"
      -- Gowron, Star Trek TNG.

Re: Marks woes on upgrade from oort 0.03 -> 0.04.

[Paul Jarc]

Karra <karra@cs.utah.edu> wrote:
> How about inserting the following into the manual?
>
> --- gnus.texi.old       Sun Jan 13 05:36:43 2002
> +++ gnus.texi   Sun Jan 13 05:42:19 2002
> @@ -13688,6 +13688,10 @@
>  to restore the group (after restoring the backup into the nnml
>  directory).
>
> +If for some reason you believe your @file{.marks} files are screwed
> +up, you can just delete them all.  Gnus will then correctly regenerate
> +them next time it starts.
> +

Better also include a note that this will not necessarily always be
true in future versions.  Right now, .newsrc.eld is storing a
redundant copy of the same information, but that may not always be the
case.


paul

Re: Marks woes on upgrade from oort 0.03 -> 0.04.

[Lars Magne Ingebrigtsen]

Karra <karra@cs.utah.edu> writes:

> +If for some reason you believe your @file{.marks} files are screwed
> +up, you can just delete them all.  Gnus will then correctly regenerate
> +them next time it starts.

Thanks for the patch; I've applied it to Oort Gnus v0.05 (i. e., CVS).

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