Subj : Re: Top date?
To   : Jim Hanoian
From : William McBrine
Date : Mon Feb 05 2001 07:04 am

-=> Jim Hanoian wrote to William McBrine <=-

 JH> The packet list shows the month, day, time on each packet
 JH> except the top one... which shows month, day, year.

 JH> When I re-stamp the top packet, it shows correctly.

The algorithm is, if the packet is older than about 6 months (15,000,000
seconds, to be exact), it prints the year; if newer, it prints the time. I
copied this from the behavior of the "ls" command in Unix (basically the
equivalent to "dir" in DOS). If you remember, back in MultiMail < 0.26, it 
printed both the year and time, but I thought this took up too much space.

Anyway, where it gets weird is if a packet is timestamped in the _future_;  
in that case, it again prints the year instead of the time. (I'm no longer
sure why I did that, though I believe it also copies ls. I think there's
another reason, too...)

Of course, such packets shouldn't exist; but they may, if you're getting
packets from another time zone, or if the zmodem transfer doesn't handle
time zones properly, or both. I used to get future-dated packets from
Fonix, and I get packets dated way behind from Comm Port. That's why, when
I got some requests for this date-preserving behavior, I used to say that I
actually _counted_ on MultiMail changing the date, to get rid of those
screwy dates. :-) But I've come to believe that the Touch function is a
better approach.

.... ///\oo/\\\ Bugs? What bugs? ///\oo/\\\ ///\oo/\\\
--- MultiMail/Linux v0.38
 * Origin: COMM Port OS/2 juge.com 204.89.247.1 (281) 980-9671 (1:106/2000)

.