On 2026-08-21 15:06:50 +0100, Ian Collier via Mutt-dev wrote: > On Fri, Aug 21, 2026 at 03:54:03PM +0200, Vincent Lefevre wrote: > > Currently, with the following: > > > > 1. printf "\xe9" > foo > > 2. Compose a mail with Mutt and attach file "foo" (it is recognized > > as iso-8859-1, which is "é"). > > 3. recode l1..utf8 foo > > 4. Send the message. > > > Mutt doesn't give any warning > > So 'recode' saves the timestamps and puts them back after the data > is written (though curiously in the Fedora implementation it sets > the nanoseconds to zero even if they weren't zero before). > > All of which means you really want to save both the mtime and ctime > and alert if either of them is different (not just later). > > How pedantic do we want this to be? Is it a thing that happens in the > real world?
I don't know whether "recode" is used by many people, but there's also "mv". Otherwise the test could be just removed, letting the user entirely responsible on checking if an attached file gets modified. -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
