Hi Stan,
> Mutt's current behavior is consistent with elm and other mailers.
> This is traditional mbox behavior. I happen to like it.
Are there RFCs or something like that?
That is has always been so doesn't necessarily mean that it's correct.
> > Great! Developers, will you change it then? :-)
>
> I hope not. There is no need to have the mtime to be updated
> every time the ctime is updated.
What is the mtime for then?
"time of modification" sounds pretty clear to me, no?
> (Or, if there is such a need, maybe make a new variable
> "touch_folder_upon_delete" or something, with a default of "no".)
I'd be happy with that, too.
> If you have a tool that really needs to see if a file has been altered,
> it merely needs to look at the ctime rather than the mtime.
ls -t
find -newer
rsync -u
unison -times
and probably a lot more.
Unison (http://www.cis.upenn.edu/~bcpierce/unison) is the one I am using to
synchronize my files between various machines. In ists docs I find:
On Unix, we don't need to actually read the
contents of files unless they've changed, because we know that, if a
file's inode number and modtime are both the same as the last time we
looked at it, then its contents have definitely not changed.
Is the author wrong?
Thanks,
Andy.
--
Dr. Andy Spiegl, Radio Marañón, Jaén, Perú
E-Mail: [EMAIL PROTECTED], [EMAIL PROTECTED]
URL: http://spiegl.de, http://radiomaranon.org.pe
PGP/GPG: see headers
o _ _ _
------- __o __o /\_ _ \\o (_)\__/o (_) -o)
----- _`\<,_ _`\<,_ _>(_) (_)/<_ \_| \ _|/' \/ /\\
---- (_)/ (_) (_)/ (_) (_) (_) (_) (_)' _\o_ _\_v
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
