Re: Support for flat MH mailboxes

--tkMElAMwrFppLjY2
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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 stor=
ed
> 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) =3D=3D 0)
     goto out;
=20
-  rc =3D 0;
+  rc =3D 1;
=20
 out:
   mutt_buffer_pool_release (&tmp);


Olaf

--tkMElAMwrFppLjY2
Content-Type: application/pgp-signature; name=signature.asc
Content-Description: Digital signature

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEE97o7Um30LT3B+5b/86SN7mm1DoAFAmpWAcIACgkQ86SN7mm1
DoAYWRAAhQ3sB9s2Y1aIv7EtfXZtOQuC2C+ObSiL2rnQ2nJnlzfyRyuMhfuLly55
dIfZ6dxldvxW2rpkZBaaTOjwABnbNhCn9honXtIdODYIpBebaTQjjibhHbahb8Uw
nRHP1Vm/AK+X2d2NwYQZKD2e2huOPAs1LKpvSI/L/XQUHmgVg3dKC0uW/SwK5xSp
OzJyMexLu34H1s/8Z4tXru7ea5Czf6PUmspKwANV9Y4Ed/DtLXkCzhf1u2fOTHDR
IMXZBK7VDk4htzeUIw976OrStpr0cDP5X20qV5QyUL+AmnUwF+2tkFrBrlmpGcGZ
lOOdTB0Dt3ZEtPJPO6bETVStjRG3wKXI4UxMblqBe37eJbFSeIZIFHavfV5Wuvim
BfwxcCpJPwWqbQKeKe9U2vDOchkxZFpMelkV4kUhNCI6qL0H4ZYPnbz0JjkUE/A5
5j9UaUemBfP5DR7Q8W5ZYaK968VkZf1rJcAAtVmAljOJidVjhSyS96J9NVOVZGM1
6N/RezQOCLaAGhUnV/4vsNBF8RIUpcvlp0M+Bp1BS5XCqbQRp8nG8fFe0H0clAGT
DE8A78mxORrH/s98Bp0SR0R4ku7N+9kwpGVaBiM7iOcfrUK+NZSxpisx52xiUWZR
rutBHICocgjlGUpIDR1yasbOTrOJ939CXT9K7cxOfSx+LRjDWaE=
=f688
-----END PGP SIGNATURE-----

--tkMElAMwrFppLjY2--