On Tue, Jul 14, 2020 at 08:26:07AM +0200, Sebastian Stein wrote:
Kevin J. McCarthy <ke...@8t8.us> [200708 08:59]:> Perhaps some combination of settings is causing this. Would you mind > forwarding your configuration to me, so I can try to reproduce with > that?Thanks to Mike's help paring down his configuration to a minimal reproduce, I was able to find the problem. I'll get a patch to stable tomorrow and a release out later this week.Yesterday I compiled 1.14.6 from source code, but still see it happening. Today, I had several mails in 3 different folders (Mail/folder-1-file, Mail/folder-2-file), but only one of them showed up as being new.
Your original mail (<20200106150335.ga10...@hpfsc.de>) reported you were seeing the problem with 1.10.1, but then it stopped with 1.13.2.
Unfortunately, the problem Mike reported first showed up in Mutt 1.11.0. If you are still having the problem with 1.14.6 it may be a different issue.
Mike's reported bug was triggered by relative path mailboxes. Instead of:
set folder = "~/Mail" mailboxes =a =b =c he had: set folder = "~/Mail" mailboxes a b cwhere a, b, and c were then resolved relative to the mutt starting directory, instead of under $folder. I made a mistake with the system call, forgetting a flag to ensure relative path behavior when resetting the access-time.
Do you have any minimal mutt config I could try to see if the problem goes away? My config was created like 20 years ago and not sure if there is anything weird in.
If the above isn't the problem, I'm afraid I would need your help in paring down to a minimal reproduce. -- Kevin J. McCarthy GPG Fingerprint: 8975 A9B3 3AA3 7910 385C 5308 ADEF 7684 8031 6BDA
signature.asc
Description: PGP signature
