Following on some discussions on the nmh list, I observed a problem with the local time display in exmh (which is doing what I think should be the default for nmh - that is, displaying both th original (sender) Date: header with the local time appended. Except that it wasn't working in the case that raised the issue on the nmh list - messages with +0000 listed in the Date header - nor for that matter, any other +NNNN zone (it worked fine for -NNNN and for the alphabetic zone names from rfc822). This looks like an underlying problem in tcl's clock scan code - but in the case whre no format string is provided, which the tcl doc says is obsolete, and shouldn't be used. Giving a suitable format string (after a little massaging of the input string to remove comments) seems to make it work. Below is a patch that should fix it - along with not displaying any local time in the case where the zone is given as -0000 (ie: unknown). kre ps: Note that there's actually still a bug in the unusual case where the sender's, and local, timezones are different by exactly 24 hours - but that's so rare it probably isn't worth fixing.
MIME-TIM
Description: MIME-TIME-PATCH
_______________________________________________ Nmh-workers mailing list Nmh-workers(_at_)nongnu(_dot_)org https://lists.nongnu.org/mailman/listinfo/nmh-workers