From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Kevin Foley <kevin@kevinjfoley.me>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Add notmuch-show-local-dates option
Date: Fri, 03 Jul 2020 17:37:30 -0400 [thread overview]
Message-ID: <87lfk0th45.fsf@fifthhorseman.net> (raw)
In-Reply-To: <m2h7uptw1x.fsf@Kevins-MBP.home.lan>
[-- Attachment #1.1: Type: text/plain, Size: 2373 bytes --]
On Thu 2020-07-02 18:02:34 -0400, Kevin Foley wrote:
> Daniel Kahn Gillmor <dkg@fifthhorseman.net> 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 (see below)
>> - "only", shows only the timestamp in localtime
>>
>
> I feel like "only" makes more sense as the option to be used for t, and
> having "both" as another option.
I'm fine either way.
>> so if your system is TZ=UTC, and notmuch-show-date-header-localtime is
>> set to t, and you're looking at a message sent from TZ=America/New_York,
>> you might see:
>>
>> Date: Thu, 02 Jul 2020 19:34:53 +0000 (Thu, 02 Jul 2020 15:34:53 -0400)
>
> Actually, seeing it written out here makes me realize some people could
> potentially prefer:
>
> Date: {sent-tz-datetime} ({system-tz-datetime})
>
> or some other kind of formatting.
>
> Would it make sense to allow a function instead of "both", which would
> be passed the time and let the user return it formatted how they would
> like? Or is that over-complicating things?
For a toolkit, i like the idea of a function. For an end-user-facing
MUA, i like opinionated decisions that do obviously the right thing,
without requiring the user to fiddle with anything.
We're struggling a bit here because notmuch-emacs is sort of in the
middle of these two things -- sometimes the one, other times the other.
Pushing on the "just do the right thing" front:
What if there were no configuration variable at all, and it just always
shows "both" ? Or, even cleverer, what if it only shows both if the
current TZ differs from the sender's TZ?
So if i'm in TZ=America/New_York, and the sender is in
TZ=America/New_York, i would just see the normal header:
Date: Fri, 03 Jul 2020 13:22:36 -0400
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
TZ=America/New_York or TZ=America/Manaus)
Is there anyone who would complain about this just being the default
behavior -- with no additional settings to change?
--dkg
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
[-- Attachment #2: Type: text/plain, Size: 158 bytes --]
_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org
next prev parent reply other threads:[~2020-07-03 21:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 13:30 [PATCH] emacs: Add notmuch-show-local-dates option Kevin J. Foley
2020-07-02 19:38 ` Daniel Kahn Gillmor
2020-07-02 22:02 ` Kevin Foley
2020-07-03 21:37 ` Daniel Kahn Gillmor [this message]
2020-07-03 22:58 ` David Bremner
2020-07-04 13:26 ` Daniel Kahn Gillmor
2020-07-04 13:32 ` Tomi Ollila
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfk0th45.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=kevin@kevinjfoley.me \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).