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

[Karra <karra@cs.utah.edu>]

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.