all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: 74869@debbugs.gnu.org
Cc: Richard Lawrence <rwl@recursewithless.net>
Subject: bug#74869: Fwd: [PATCH] Add predicates for decoded times and time deltas
Date: Sun, 29 Dec 2024 11:18:33 -0800	[thread overview]
Message-ID: <7be82ecf-0d4f-488a-94ae-3f39fe886edb@cs.ucla.edu> (raw)
In-Reply-To: <e6537a9d-3f74-46a0-9bbd-ef63d045f4c2@cs.ucla.edu>

Forwarding another mis-addressed email of mine.


-------- Forwarded Message --------
Subject: Re: [PATCH] Add predicates for decoded times and time deltas
Date: Sat, 28 Dec 2024 09:26:23 -0800
From: Paul Eggert <eggert@cs.ucla.edu>
To: Richard Lawrence <rwl@recursewithless.net>
CC: 74689@debbugs.gnu.org

On 12/28/24 07:56, Richard Lawrence wrote:
> I need to use
> `calendar-extract-month' with a plain date value, but
> `decoded-time-month' with a date-time value. I need type predicates to
> do such dispatching.

Not necessarily; you can instead try each function in turn and use the 
first that works.

I have some qualms about saying that decoded times are a "type". Whether 
a decoded time is valid depends on the timezone: (0 30 2 10 3 2024 0 t 
-21600) is a valid decoded time in Phoenix but not in Denver, because 
clocks sprang forward over that time in Denver but not in Phoenix. When 
data interpretation gets that complicated, the Emacs notion of "type" is 
not always the best.





       reply	other threads:[~2024-12-29 19:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <e6537a9d-3f74-46a0-9bbd-ef63d045f4c2@cs.ucla.edu>
2024-12-29 19:18 ` Paul Eggert [this message]
     [not found] <468ca0ab-a4aa-41ed-8f6c-260940f3f9f3@cs.ucla.edu>
2024-12-29 19:17 ` bug#74869: Fwd: [PATCH] Add predicates for decoded times and time deltas Paul Eggert

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7be82ecf-0d4f-488a-94ae-3f39fe886edb@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=74869@debbugs.gnu.org \
    --cc=rwl@recursewithless.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.