On Tue, May 12, 2020 at 02:43:44AM +0200, Vincent Lefevre wrote:
Now, even if dotlocking isn't dropped, I don't think that it should be mandatory. IMHO,
I'll look into this, but it should be no surprise that I'd prefer to make it "opt-out" rather than "opt-in".
* one should be able to specify the location of the dotlock program at run time (so that non-root users could install a more recent version of Mutt in their home directory);
I think you can already, by setting $dotlock_program. (Assuming the external dotlock program is configured).
* one should be able to use dotlocking in an optional way, i.e. just as an additional security, in addition to fcntl: if there is no sufficient directory permission to create a lock file, then ignore dotlocking and just rely on fcntl (which should be fine for most users).
Right now, the code will first perform fcntl/flock and then *also* perform a dotlock.
I guess you could disable the dotlock by setting $dotlock_program to "/bin/true".
-- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
