Hi!
It would be nice to have an example for using date2local in the base
nmh distribution.
Maybe we could get a scan.timely.local which works exactly like
scan.timely but with the added benefit of recalculating the date to
local time so that scan listings involving people on several conti-
nents get sorted in real time order and not by their local time w/o
regarding the time zone.
The best would of course be to modify scan.timely if there are no
objections. Those using it already without caring about this won't
notice much of a difference (besides not having to remember the
sender's time zone and adjusting the time manually - scan.timely
doesn't display the time zone!) I think.
The rest won't be surprised by the (at first sight) seemingly nonsense
scan outputs after sorting by time w/o this modification. It looks
unsorted regarding the messages which arrived in the last 24 hours if
they are from several time zones.
The unified diff for nmh 0.23's scan.timely is:
--- /usr/local/etc/nmh/scan.timely Sun Mar 22 21:46:29 1998
+++ scan.timely.local Sun Jul 5 21:32:39 1998
@@ -1,5 +1,6 @@
%4(msg)%<(cur)+%| %>%<{replied}-%?{encrypted}E%| %>\
%(void(rclock{date}))\
+%(void(date2local{date}))\
%<(gt 15768000)%03(month{date})%(void(year{date}))%02(modulo 100)\
%?(gt 604800)%02(mday{date})%03(month{date})\
%?(gt 86400) %(day{date}) %|\
Stefan.
--
Stefan Eggers Lu4 yao2 zhi1 ma3 li4,
Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1.
51109 Koeln
Federal Republic of Germany