From: Jean Louis <bugs@gnu.support>
To: Jude DaShiell <jdashiel@panix.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: even elder races get tired of waiting
Date: Mon, 22 Mar 2021 10:54:21 +0300 [thread overview]
Message-ID: <YFhNLYRQfKIRvUeD@protected.localdomain> (raw)
In-Reply-To: <alpine.NEB.2.23.451.2103211516280.19720@panix1.panix.com>
* Jude DaShiell <jdashiel@panix.com> [2021-03-21 22:24]:
> Use of cal with a month number and a year number to get a weekday of a
> particular date can make work a little easier.
How to do that?
> This is for really long time periods and only inside the gregorian calendar
> constraints since outside of those constraints things get really wild as a
> result of compound errors.
> With that weekday in mind subtracting a year when you won't land in a leap
> year or adding a year when you won't land in a leap year, subtract or add
> one weekday to get the correct weekday for that date in those years. If you
> will land in a leap year, subtract or add two weekdays to get the correct
> weekday. Modulus the weekday by 7 to keep it in whichever range you prefer
> to use..
I would like to use Emacs functions to calculate the new DATE after
SOME NUMBER OF DAYS from STARTING DATE.
For leap years it looks like PostgreSQL isdoing it right:
(defun days-from (from-date to-date)
"Returns days passed from FROM-DATE to TO-DATE in format YYYY-MM-DD."
(string-to-number
(string-trim
(shell-command-to-string
(format "psql -Aqtc \"SELECT abs('%s'::date - '%s'::date)\"" to-date from-date)))))
(days-from "2020-02-28" "2020-03-01") => 2
(days-from "2021-02-28" "2021-03-01") => 1
prev parent reply other threads:[~2021-03-22 7:54 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-20 20:37 even elder races get tired of waiting Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-21 14:01 ` Jean Louis
2021-03-21 14:19 ` Jean Louis
2021-03-21 15:12 ` Jude DaShiell
2021-03-21 17:10 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-21 17:29 ` Jean Louis
2021-03-21 17:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 7:21 ` Jean Louis
2021-03-21 22:30 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 7:48 ` Jean Louis
2021-03-22 18:29 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 19:10 ` Jean Louis
2021-03-22 19:47 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 20:31 ` Jean Louis
2021-03-22 21:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 21:40 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 22:43 ` Jean Louis
2021-03-22 23:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 23:38 ` Jean Louis
2021-03-22 23:52 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 8:42 ` Jean Louis
2021-03-22 18:31 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 19:21 ` Jean Louis
2021-03-21 17:13 ` Jean Louis
2021-03-21 19:24 ` Jude DaShiell
2021-03-21 22:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-03-22 7:54 ` Jean Louis [this message]
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=YFhNLYRQfKIRvUeD@protected.localdomain \
--to=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=jdashiel@panix.com \
/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.
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).