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
I then renamed the second one as 05657500.TBS, returned to Arachne and
checked their order. It was the same as before the renaming.
So the points are:
1. That Arachne saves the modified message under a new name; and
2. that the sort is on the time/date stamp.
> I'll look into makeing a slight modification in the code
> so that we can have the option of doing just that.
> Let's say... a new Arachne.cfg value.
> KeepDate Yes
> Will default to 'No' if that line is not present in arachne.cfg
That would probably work, although it is useful to know the true date of
the last mod.
I think what would work better would be something like
OutboxModifyKeepName Yes:No
OutboxSortBy Name:Date:Size:None
from Greg Mayman, in Adelaide, South Australia
Home of the Bay to Birwood Vintage and Classic motor runs
http://www.baytobirdwood.com.au
Visit me at http://homepages.picknowl.com.au/greg_mayman/default.htm
-- Arachne V1.71;UE01, NON-COMMERCIAL copy, http://arachne.cz/
