unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: 72570@debbugs.gnu.org, eggert@cs.ucla.edu
Subject: bug#72570: 31.0.50; Regression in date-to-time
Date: Mon, 12 Aug 2024 16:26:24 +0300	[thread overview]
Message-ID: <86v805hny7.fsf@gnu.org> (raw)
In-Reply-To: <uv8057vm1@gentoo.org> (message from Ulrich Mueller on Mon, 12 Aug 2024 14:51:02 +0200)

> From: Ulrich Mueller <ulm@gentoo.org>
> Cc: Paul Eggert <eggert@cs.ucla.edu>,  72570@debbugs.gnu.org
> Date: Mon, 12 Aug 2024 14:51:02 +0200
> 
> > But that is not necessarily incorrect, because several time-conversion
> > functions, including those involved in this issue, don't document
> > their assumptions about time-zone when it is omitted.  This includes
> > parse-time-string and iso8601-parse.  Since these functions don't
> > document this aspect, and the code involved in the above snippet is
> > quite convoluted, it is hard for me to decide which part of what
> > function needs to be fixed.
> 
> Well, parse-time-string doesn't make any assumptions about the timezone.
> It will return a list with nil in its TZ element, if it cannot extract
> any timezone info from the string.
> 
> Same for iso8601-parse, the returned TZ is nil if it is not present in
> the argument string.

Yes, but what does nil as timezone mean, when you later interpret the
time values?  Is it UTC or is it local time?





  reply	other threads:[~2024-08-12 13:26 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 [this message]
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
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=86v805hny7.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=72570@debbugs.gnu.org \
    --cc=eggert@cs.ucla.edu \
    --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).