Try feeding mhstore from a file instead of a message, something like:
Alas, mhstore -file did not solve the problem; mhfixmsg already was using
implicit -file, $1 is an absolute path
Okay, some more odd evidence
"WORKING" state w/o mhstore
From within mime-add-hook mark reports this, both before and after the -add
cur:
But cat .mh_sequences gives the following, before and after
cur: 29
unseen: 23-28
pseq: 23-28
mark from the command line gives the following after, but matches cat before
cur: 29
unseen: 23-29
pseq: 23-29
BROKEN with mhstore
From within mime-add-hook mark reports this, both before -add
cur:
...and after
cur:
unseen: 30
But cat .mh_sequences gives the following, before
cur: 30
unseen: 23-29
pseq: 23-29
...and after
unseen: 30
I seem to have found a workaround that works, even with the call to
mhstore, although it still gives inconsistent ouput like above;
with "pseq: 30" instead of "cur:" The workaround is including the
sequence itself in the messages to add to the sequence i.e;
mark unseen $MSG -add -seq unseen -nozero
_______________________________________________
Nmh-workers mailing list
Nmh-workers(_at_)nongnu(_dot_)org
https://lists.nongnu.org/mailman/listinfo/nmh-workers