From: Paul Eggert <eggert@cs.ucla.edu>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: Eli Zaretskii <eliz@gnu.org>, 72570@debbugs.gnu.org
Subject: bug#72570: 31.0.50; Regression in date-to-time
Date: Tue, 13 Aug 2024 12:39:48 -0700 [thread overview]
Message-ID: <55718663-6c04-4f97-b3cb-122c924895c2@cs.ucla.edu> (raw)
In-Reply-To: <uh6bp6k6l@gentoo.org>
On 2024-08-12 22:55, Ulrich Mueller wrote:
> don't we have a chicken-and-egg problem? We'd need the UTC timestamp
> to infer the timezone, but the timezone to calculate the timestamp?
You're quite right that we have a chicken and egg problem, and that no
solution will be perfect here. My point was that using a heuristic would
be better than nothing, if the goal is to infer timezone from incomplete
input. That's why timezone-fix-time uses this heuristic.
I continue to think that your idea of changing date-to-time to default
to the local time zone is the best way to move forward. How about this
idea for doing it?
* Change the doc to say this. This is a simple change, and it reflects
existing behavior better.
* Change date-to-time so that if it falls back on
timezone-make-date-arpa standard, it insists that the string denotes a
time zone; if the string lacks a time zone it errors out with "Invalid
date", which it already does with invalid dates.
next prev parent reply other threads:[~2024-08-13 19:39 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 8:57 bug#72570: 31.0.50; Regression in date-to-time Ulrich Mueller
2024-08-12 7:27 ` Ulrich Mueller
2024-08-12 8:18 ` Ulrich Mueller
2024-08-12 11:42 ` Eli Zaretskii
2024-08-12 12:51 ` Ulrich Mueller
2024-08-12 13:26 ` Eli Zaretskii
2024-08-12 13:48 ` Ulrich Mueller
2024-08-12 14:30 ` Eli Zaretskii
2024-08-12 22:03 ` Paul Eggert
2024-08-13 5:55 ` Ulrich Mueller
2024-08-13 19:39 ` Paul Eggert [this message]
2024-08-13 21:11 ` Ulrich Mueller
2024-08-13 21:19 ` Paul Eggert
2024-08-14 8:12 ` Ulrich Mueller
2024-08-14 14:09 ` Ulrich Mueller
2024-08-15 3:27 ` Paul Eggert
2024-08-15 4:35 ` Ulrich Mueller
2024-08-15 6:26 ` Paul Eggert
2024-08-15 6:45 ` Eli Zaretskii
2024-08-15 7:18 ` Ulrich Mueller
2024-08-15 7:22 ` Eli Zaretskii
2024-08-13 11:15 ` Eli Zaretskii
2024-08-13 15:09 ` Ulrich Mueller
2024-08-13 15:36 ` Eli Zaretskii
2024-08-13 19:59 ` Paul Eggert
2024-08-14 8:37 ` Eli Zaretskii
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://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=55718663-6c04-4f97-b3cb-122c924895c2@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=72570@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=ulm@gentoo.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://git.savannah.gnu.org/cgit/emacs.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).