On Tue, 16 Dec 2014 23:24:30 -0500 David Levine <levinedl@acm.org> sez:
Bob wrote:
Ah, okay, that works! My man page is for the older NMH 1.5,
and says something critically different at this point:
zone date integer timezone in hours
tzone date string timezone string
Oh yeah, that was fixed after 1.6 went out. Otherwise, we'd
be asking you why you're still using 1.5 :-)
Oh, that's a perfectly valid question. B-)
By the way, there seems to be a formatting bug with "zone"
when specifying wide fields with "leading" zeros. For example,
if you specify the Date: field this way
Date:formatfield="%<(nodate{text})%{text}%|%(pretty{text})%(void(szone{text}))%<(eq
1) %(date2local{text})%08(zone{text})%>%>"
You get
Tue, 16 Dec 2014 23:24:30 -0500 0000-480
I'm guessing negative integers were not expected by the
padding function? And perhaps it was also fixed with 1.6
(or afterward)?
Bob
_______________________________________________
Nmh-workers mailing list
Nmh-workers@nongnu.org
https://lists.nongnu.org/mailman/listinfo/nmh-workers