unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: Paul Eggert <eggert@cs.ucla.edu>
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 07:55:30 +0200	[thread overview]
Message-ID: <uh6bp6k6l@gentoo.org> (raw)
In-Reply-To: <892ebc72-1020-471a-bdcd-8e8da10d61dd@cs.ucla.edu> (Paul Eggert's message of "Mon, 12 Aug 2024 15:03:46 -0700")

>>>>> On Tue, 13 Aug 2024, Paul Eggert wrote:

> As for the original issue, I tend to agree with Ulrich that
> date-to-time should default to local time. This would need changes to
> both documentation and to code. Ulrich mentioned the following
> potential issue with this idea:

>> The problem is that timezone-make-date-arpa-standard would need an
>> explicit timezone as its second argument, which we don't know.

> The code could use timezone-time-zone-from-absolute to infer a
> timezone. timezone-fix-time already does this sort of thing.
> Admittedly getting the details right could be a bit tricky, and there
> is no perfect solution in this area (certainly timezone-fix-time is
> flawed). It might be good enough, though.

IIUC timezone-time-zone-from-absolute expects the SECONDS argument
to be seconds since midnight in UTC (again, not documented). In the
Europe/Berlin timezone (DST starts at 02:00 local time), I get this:

  (timezone-time-zone-from-absolute
   (timezone-absolute-from-gregorian 3 31 2024)
   (* 1 60 60))

  (7200 "CEST")

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





  reply	other threads:[~2024-08-13  5:55 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 [this message]
2024-08-13 19:39       ` Paul Eggert
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=uh6bp6k6l@gentoo.org \
    --to=ulm@gentoo.org \
    --cc=72570@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --cc=eliz@gnu.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).