Re: [Nmh-workers] problem with mark zeroing out sequences

[Ken Hornstein]

>I suppose I could try, but I've not used a C debugger
>
>Hmm, on a hunch I just discovered that somehow the call to mhstore in
>mime-add-hook's for loop is the trigger... of course that's the raison
>d'etre of the script :-/

Well, think about what's going on.  You're changing sequences in the
middle of an operation which is changing sequences.  At a minimum you're
going to be on the fringe of supported behavior.

Are you using 1.3 (ewww), 1.5, or post-1.5 for your nmh implementation?
I ask because as part of the locking rototilling I did that went in
post-1.5 sequences handling got changed in inc; the sequence file is
re-read after all messages have been incorporated and then changed.
Before that change inc would read the sequence file at startup,
incorporate messages, and then update the sequence file based on what it
read at startup.

--Ken