On 07Dec2012 18:40, Chris Green <c...@isbd.net> wrote: | On Fri, Dec 07, 2012 at 10:28:12AM -0800, Michael Elkins wrote: | > On Fri, Dec 07, 2012 at 06:22:32PM +0000, Chris Green wrote: | > >How does mutt detect no change to the temporary file when one hits | > >R[eply] but then makes no change to the file? | > | > Yes, if the modification time on the file is unchanged. See | > $abort_unmodified to change this behavior. | | Thank you, I sort of want the opposite, a way to fool mutt into thinking | the file *hasn't* been modified. I'm editing the file via a wrapper | script and that always changes the modification time even if the file | hasn't actually changed.
I have a script called rewriteif for exactly this purpose - I used it a lot. You work on a copy (or generate new data outright, depends on the use case) and feed the result to: rewriteif original-file-name It compares both and only overwrites the original if they differ. The script is here: https://bitbucket.org/cameron_simpson/css/src/tip/bin/rewriteif but if you'd rather bare shell the logic looks like: cp original tempfile work on tempfile cmp -s tempfile original || cp tempfile original rm tempfile | I think I will have to change how my wrapper script works to prevent it | copying the file *unless* it actually changes it. Yep. See above. Cheers, -- Cameron Simpson <c...@zip.com.au> There are old climbers, and there are bold climbers; but there are no old bold climbers.
