unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Kevin Foley <kevin@kevinjfoley.me>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: Add notmuch-show-local-dates option
Date: Thu, 02 Jul 2020 18:02:34 -0400	[thread overview]
Message-ID: <m2h7uptw1x.fsf@Kevins-MBP.home.lan> (raw)
In-Reply-To: <87r1ttu2pb.fsf@fifthhorseman.net>

Daniel Kahn Gillmor <dkg@fifthhorseman.net> 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 header that the sender sent.
> But a boolean setting doesn't give me much room to express that
> preference.

Good point, this is something I hadn't considered but I agree would be
useful to allow.

> This comment says "time", but the emacs config variable name says
> "dates".  This confusion is worse because the Date: header actually
> contains a timestamp, not a date ☹
>
> Perhaps we should rename the variable notmuch-show-date-header-localtime,

I struggled with a name for the reasons you listed =), I think your
proposed name is much clearer and will use that. 

> 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.

> 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?

Kevin


_______________________________________________
notmuch mailing list -- notmuch@notmuchmail.org
To unsubscribe send an email to notmuch-leave@notmuchmail.org

  reply	other threads:[~2020-07-02 22:03 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 [this message]
2020-07-03 21:37     ` Daniel Kahn Gillmor
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=m2h7uptw1x.fsf@Kevins-MBP.home.lan \
    --to=kevin@kevinjfoley.me \
    --cc=dkg@fifthhorseman.net \
    --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).