On Tue, Jul 14, Kevin J. McCarthy wrote: > A fair amount of code is devoted to reading and updating the .mh_sequences > file, though, so I don't think it's an easy swap. Aren't some flags stored > in the .mh_sequences file too?
Given that the whole code is naive, every directory can be assumed to be
a MH mailbox. The code reads none of the checked files, and every write
to the directory may corrupt the state if the other applications use
something else than '.mh_sequences'.
Maybe the mailbox should be forced read-only unless '.mh_sequence' exists?
I use this change for the time being:
--- mh.c
+++ mh.c
@@ -2800,7 +2800,7 @@
if (access (mutt_b2s (tmp), F_OK) == 0)
goto out;
- rc = 0;
+ rc = 1;
out:
mutt_buffer_pool_release (&tmp);
Olaf
signature.asc
Description: Digital signature
