Interesting discussion this one, guys... As far as I remember, PKZIP (and perhaps also Winzip, haven't checked yet) is capable of changing the time stamp of any file it compresses/uncompresses so that you are given the option of given the original creation date to the file you are uncompressing (let's suppose it's the unzip case), or the date when it was archived, or the date of uncompression...
Arachne could and perhaps SHOULD give me the very same options, as we've seen it's possible... On the other hand, me too thinkest writing an entirley new file for any message you just "touch" isn't the wisest behaviour... haven't chekced it, however, since I use Opera for mailing and Arachne as a learning tool... (and a very good one, indeed); as well as a DOS/Linux thin and fast HTML viewer... 25/06/03 20:57:52, "Greg Mayman" <[EMAIL PROTECTED]> escribi�: >On Wed, 25 Jun 2003 01:24:37 -0400, Glenn McCorkle wrote: > >>> I wonder why Arachne writes the modified version as a new message, >>> rather than just saving it under the original name. > >> For the same reason that *any* file we modify >> and then save to disk gets 're-dated'. ;-) > >No Glenn, I said "under the original NAME". > >For example I wrote one message to the outbox and checked it under DOS >DIR. At that stage it was named 05657326.TBS. > >I then modified the message and rechecked. It was now named 05657414.TBS >so it is obvious that Arachne creates a NEW file after a modify. > >To test the sorting order, I wrote two messages to the outbox a few >minutes apart. > >DIR showed the two files as > 05657558.TBS 25-06-03 17:13 >and 05657573.TBS 25-06-03 17:15 > [mensaje truncado]
