On Fri 2020-07-03 19:58:23 -0300, David Bremner wrote:
> The bikeshed must be blue! Uh, I mean what about narrowish screens (80
> columns or so) and or deeply indented threads?
You mean what should happen to messages with headers that are much
longer, like:
To: David Bremner , Kevin Foley ,
notm
On Fri, Jul 03 2020, David Bremner wrote:
> Daniel Kahn Gillmor writes:
>
>> But if the sender is in TZ=Europe/Berlin, i would see:
>>
>> Date: Fri, 03 Jul 2020 13:22:36 -0400 [Fri, 03 Jul 2020 19:22:36 +0200]
>>
>> (Note that RFC 5322 Date format shows the hour offset, but not the
>> actual
Daniel Kahn Gillmor writes:
> But if the sender is in TZ=Europe/Berlin, i would see:
>
> Date: Fri, 03 Jul 2020 13:22:36 -0400 [Fri, 03 Jul 2020 19:22:36 +0200]
>
> (Note that RFC 5322 Date format shows the hour offset, but not the
> actual TZ -- i can't tell from -0400 whether someone is in
On Thu 2020-07-02 18:02:34 -0400, Kevin Foley wrote:
> Daniel Kahn Gillmor writes:
>> and it could take three values:
>>
>> - nil (default), shows the Date: header as received
>> - t, shows the timestamp from the Date: header in local time,
>>with the as-received header in parens afterward
Daniel Kahn Gillmor writes:
> But, setting this to t hides the sender's TZ from the viewer -- and i
> often find it useful to learn the sender's TZ from the Date: header.
>
> What would be really useful for me is to see the Date header represented
> both ways: in my local time *and* the Date head
This proposed notmuch-show-local-dates feature is a nice one. It
renders the Date header in a format that is likely to be more useful to
the viewer. I certainly find this more useful than having to do the
TZ conversions in my head.
But, setting this to t hides the sender's TZ from the viewer --
Allows users to specify they'd like dates to be displayed in local time
---
emacs/notmuch-show.el | 12 +
test/T310-emacs.sh| 9 +++
.../notmuch-show-message-with-local-dates | 25 +++
3 files changed, 46 insertio
