On Wed, Aug 19, 2026 at 11:24:50AM +0800, Kevin J. McCarthy wrote:
On Mon, Aug 17, 2026 at 07:38:22PM +0200, Vincent Lefevre wrote:
This has just occurred again (this time in the train).

In case this matters:

qaa:~[77%]> /usr/bin/stat /var/tmp/mutt-qaa-1000-2859-6061931621091561353
File: /var/tmp/mutt-qaa-1000-2859-6061931621091561353
Size: 2241            Blocks: 8          IO Block: 4096   regular file
Device: 254,1   Inode: 13252685    Links: 1
Access: (0600/-rw-------)  Uid: ( 1000/  vinc17)   Gid: ( 1000/  vinc17)
Access: 2026-08-17 19:30:55.000617603 +0200
Modify: 2026-08-17 19:30:55.000607627 +0200
Change: 2026-08-17 19:30:55.000607627 +0200
Birth: 2026-08-17 19:30:55.000440459 +0200

I can notice 2 things:

1. The times are just after 19:30:55.

2. The Modify and Change times are not equal to the Birth time,
which seems unusual

Mutt creates the file and then invokes the editor. So the birth time should be when mutt creates it. But I'm skeptical about the minuscule gap between birth and modify unless you are somehow scripting the test.

Oh, yes, I forgot about emacs backup-by-copying. That defaults nil (I have mine set to t for a long time). If you have the as the default perhaps it's emacs that is recreating the file. Maybe it does so in two steps, leaving to the tiny difference in birth and modify time?

--
Kevin J. McCarthy
GPG Fingerprint: 8975 A9B3 3AA3 7910 385C  5308 ADEF 7684 8031 6BDA

Attachment: signature.asc
Description: PGP signature

Reply via email to