trouble with .marks

trouble with .marks

[Colin Walters]

Hello,

I had been using Oort Gnus for a while until about two weeks ago, when
I started to have some random type errors, and I thought I'd downgrade
to the stock Gnus 5.9 from Emacs 21.

I'd like to try Oort again (for the GNUPG integration), now that I
have time to debug the type errors, but unfortunately I have leftover
.marks files from when I was using Oort.  Can I just delete those, and
will everything be regenerated when I upgrade to Oort again?  In other
words, I'd like to keep my current ranges of read articles and such.

Thanks!

Re: trouble with .marks

[Simon Josefsson]

On 7 Oct 2001, Colin Walters wrote:

> Hello,
>
> I had been using Oort Gnus for a while until about two weeks ago, when
> I started to have some random type errors, and I thought I'd downgrade
> to the stock Gnus 5.9 from Emacs 21.
>
> I'd like to try Oort again (for the GNUPG integration), now that I
> have time to debug the type errors, but unfortunately I have leftover
> .marks files from when I was using Oort.  Can I just delete those, and
> will everything be regenerated when I upgrade to Oort again?

Yes.

Maybe we should fix this, even though it probably isn't the only problem
you would see when upgrading->downgrading->upgrading.  Looking at
`gnus-newsrc-file-version' like someone suggested is probably a simple and
working solution.

Re: trouble with .marks

[Kai Großjohann]

Colin Walters <walters@debian.org> writes:

> I'd like to try Oort again (for the GNUPG integration), now that I
> have time to debug the type errors, but unfortunately I have leftover
> .marks files from when I was using Oort.  Can I just delete those, and
> will everything be regenerated when I upgrade to Oort again?  In other
> words, I'd like to keep my current ranges of read articles and such.

I think that should work.  After all, Simon's code takes care to
upgrade once, so it'll upgrade twice, too.

kai
-- 
Linux provides a nice `poweroff' command, but where is `poweron'?

Re: trouble with .marks

[Colin Walters]

Simon Josefsson <jas@extundo.com> writes:

> Yes.

I somehow missed seeing the thread Lloyd started about this same
subject before I sent my original message.  My apologies.

Anyways, removing the .marks files and upgrading to Oort again works
just fine.  Now...on to debugging.

Re: trouble with .marks

[Dan Christensen]

Simon Josefsson <jas@extundo.com> writes:

> Maybe we should fix this, even though it probably isn't the only problem
> you would see when upgrading->downgrading->upgrading.  Looking at
> `gnus-newsrc-file-version' like someone suggested is probably a simple and
> working solution.

Will this problem also happen if the user sets nnfolder-marks-is-evil
to t then nil then t?  I guess one solution is to have Gnus remove
the .mrk files it finds if nnfolder-marks-is-evil is set to nil
and Gnus is changing the marks for that group in .newsrc.eld.

Alternatively, if nnfolder-marks-is-evil is t, Gnus could not store
the marks in .newsrc.eld at all.  If the variable is set to nil,
Gnus could read the .mrk file one last time, update .newsrc.eld,
and then remove the .mrk file.

Storing the same information in more than one place is asking
for problems of this sort, so the proposal is to never do this.

All of the above applies to nnml too, of course.

-- 
Dan Christensen
jdc+news@uwo.ca