From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1 ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms11 with LMTPS id IOFvOTSl/15pBQAA0tVLHw (envelope-from ) for ; Fri, 03 Jul 2020 21:37:56 +0000 Received: from aspmx1.migadu.com ([2001:41d0:2:4a6f::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1 with LMTPS id KHGvNDSl/16qRwAAbx9fmQ (envelope-from ) for ; Fri, 03 Jul 2020 21:37:56 +0000 Received: from mail.notmuchmail.org (nmbug.tethera.net [IPv6:2607:5300:201:3100::1657]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) server-signature RSA-PSS (4096 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 6042E94030A for ; Fri, 3 Jul 2020 21:37:55 +0000 (UTC) Received: from [144.217.243.247] (localhost [127.0.0.1]) by mail.notmuchmail.org (Postfix) with ESMTP id 4231C1FA7D; Fri, 3 Jul 2020 17:37:44 -0400 (EDT) Received: from che.mayfirst.org (che.mayfirst.org [IPv6:2001:470:1:116::7]) by mail.notmuchmail.org (Postfix) with ESMTPS id 82D8C1F9C9 for ; Fri, 3 Jul 2020 17:37:41 -0400 (EDT) DKIM-Signature: v=1; a=ed25519-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019; t=1593812258; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=1e0pzpJb+W+fjeaM1k8/4f8yhpXPPD+pkjaojsMBi08=; b=72Uzo1e/HCu/tJRYfL9di1OoDF8G/UoGb7Y1gAMOEDsqv8bimqM0LRFpNaWmpzV6tjLXY zg5uH7maO+rJ2hDBg== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=fifthhorseman.net; i=@fifthhorseman.net; q=dns/txt; s=2019rsa; t=1593812258; h=from : to : subject : in-reply-to : references : date : message-id : mime-version : content-type : from; bh=1e0pzpJb+W+fjeaM1k8/4f8yhpXPPD+pkjaojsMBi08=; b=DNCSe6DupIt79/8jmBtFAA/FDxZoRlY8R2QLK2luFi49XeULoRB2ZLXy74UGOUDmSvCER GkK5P0p8v52WRshnejPUkLkyqO2kAoXwzrQF/u2Zfaq1mX7ycAXZFuaRHgiyh6WtB/O5j9u RMJvELXwCjGTML0PlKY1PeI9V3vFv+ESxkrJmpwXDTEEnl5G1Wc/tbBsb/ysk/A6WIa6iRh UQKjqtZ8Vgz30Ug6919AFHVveRGxXS0CZmrPSD5lvViCdAehyCGXOXlrEsZT+g/vY8NtMvc QE/341MtgCtZReZIPSYWoxQtQs+4iJziyoLZy1uLHXt70lkHWWWJxp7+GQdw== Received: from fifthhorseman.net (unknown [IPv6:2001:470:1f07:60d:f2de:f1ff:fec3:d109]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by che.mayfirst.org (Postfix) with ESMTPSA id A2253F9A6; Fri, 3 Jul 2020 17:37:35 -0400 (EDT) Received: by fifthhorseman.net (Postfix, from userid 1000) id E2B6220295; Fri, 3 Jul 2020 17:37:31 -0400 (EDT) From: Daniel Kahn Gillmor To: Kevin Foley , notmuch@notmuchmail.org Subject: Re: [PATCH] emacs: Add notmuch-show-local-dates option In-Reply-To: References: <20200625133016.29701-1-kevin@kevinjfoley.me> <87r1ttu2pb.fsf@fifthhorseman.net> Autocrypt: addr=dkg@fifthhorseman.net; prefer-encrypt=mutual; keydata= mDMEXEK/AhYJKwYBBAHaRw8BAQdAr/gSROcn+6m8ijTN0DV9AahoHGafy52RRkhCZVwxhEe0K0Rh bmllbCBLYWhuIEdpbGxtb3IgPGRrZ0BmaWZ0aGhvcnNlbWFuLm5ldD6ImQQTFggAQQIbAQULCQgH AgYVCgkICwIEFgIDAQIeAQIXgAIZARYhBMS8Lds4zOlkhevpwvIGkReQOOXGBQJd5Hw3BQkFpJWB AAoJEPIGkReQOOXGDYEA/j0ERjPxDleKMZ2LDcWc/3o5cLFwAVzBKQHppu0Be5IWAP0aeTnyEqlp RTE7M8zugwkhYeUYfYu0BjecDUMnYz6iDLgzBF3kewUWCSsGAQQB2kcPAQEHQK1IuW0GZmcrs2mx CYMl8IHse0tMF8cP7eBNXevrlx2ZiPUEGBYIACYCGwIWIQTEvC3bOMzpZIXr6cLyBpEXkDjlxgUC XeR7TwUJAiGl/gCBdiAEGRYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXeR7BQAKCRDEDyVU MvKBD7KmAQCHs+7588C4jto6fMje0Nu97zzoppjJM7lrGF2rVnbHvwD+MgmGUbHzPSUrTWnZBQDi /QM595bxNrBA4N1CiXhs2AMJEPIGkReQOOXGpp0BAM7YeBnt/UNvxJAGm4DidSfHU7RDMWe6Tgux HrH21cDkAQC9leNFXJsQ7F2ZniRPHa8CkictcQEKPL8VCWpfe8LbArg4BF3ke5wSCisGAQQBl1UB BQEBB0Cf+EiAXtntQMf51xpqb6uZ5O0eCLAZtkg0SXHjA1JlEwMBCAeIfgQYFggAJhYhBMS8Lds4 zOlkhevpwvIGkReQOOXGBQJd5HucAhsMBQkCIaVkAAoJEPIGkReQOOXGdYcBANYnW7VyL2CncKH1 iO4Zr0IwfdIv6rai1PUHL98pVi3cAP9tMh85CKGDa0Xi/fptQH41meollLW5tLb/bEWMuUNuBQ== Date: Fri, 03 Jul 2020 17:37:30 -0400 Message-ID: <87lfk0th45.fsf@fifthhorseman.net> MIME-Version: 1.0 Message-ID-Hash: 5FGHCKCSCKGW4MSQOA2UWVCQXK377PRR X-Message-ID-Hash: 5FGHCKCSCKGW4MSQOA2UWVCQXK377PRR X-MailFrom: dkg@fifthhorseman.net X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-notmuch.notmuchmail.org-0; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; suspicious-header X-Mailman-Version: 3.2.1 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Help: List-Post: List-Subscribe: List-Unsubscribe: Content-Type: multipart/mixed; boundary="===============8481852079562221224==" X-Scanner: scn0 Authentication-Results: aspmx1.migadu.com; dkim=fail (body hash did not verify) header.d=fifthhorseman.net header.s=2019 header.b=72Uzo1e/; dkim=fail (body hash did not verify) header.d=fifthhorseman.net header.s=2019rsa header.b=DNCSe6Du; dmarc=fail reason="SPF not aligned (relaxed)" header.from=fifthhorseman.net (policy=none); spf=pass (aspmx1.migadu.com: domain of notmuch-bounces@notmuchmail.org designates 2607:5300:201:3100::1657 as permitted sender) smtp.mailfrom=notmuch-bounces@notmuchmail.org X-Spam-Score: -1.97 X-TUID: jbhT4MR+t32S --===============8481852079562221224== Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" --=-=-= Content-Type: text/plain Content-Transfer-Encoding: quoted-printable 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,=20 >> 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=3DUTC, and notmuch-show-date-header-localtime is >> set to t, and you're looking at a message sent from TZ=3DAmerica/New_Yor= k, >> 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=3DAmerica/New_York, and the sender is in TZ=3DAmerica/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=3DEurope/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=3DAmerica/New_York or TZ=3DAmerica/Manaus) Is there anyone who would complain about this just being the default behavior -- with no additional settings to change? --dkg --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEARYIAB0WIQQsv6x2UaqQJzY+dXHEDyVUMvKBDwUCXv+lGwAKCRDEDyVUMvKB D4q2APoCxP+jbcFggFuMKzdi+ds6w0XoKD+PVKYw3atthv2DlQEAoG6Rl78uwCwh k4VXb2JfUNirfiHrIQM1QobNp6mRhg0= =PyRS -----END PGP SIGNATURE----- --=-=-=-- --===============8481852079562221224== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ notmuch mailing list -- notmuch@notmuchmail.org To unsubscribe send an email to notmuch-leave@notmuchmail.org --===============8481852079562221224==--