From: Max Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?)
Date: Sat, 6 Apr 2024 21:52:00 +0700 [thread overview]
Message-ID: <uurnii$n7a$1@ciao.gmane.io> (raw)
In-Reply-To: <87frvzodze.fsf@localhost>
On 06/04/2024 01:34, Ihor Radchenko wrote:
> Generally, I did see several requests to change the strategy when
> calculating next month/year. However, that would be a breaking change.
> I'd only go for it if people are strongly in favor of the change.
> So, changing this to a poll.
I think the following should be taken into account: behavior of popular
calendar applications, specifications they implement, libraries that
likely used to create such applications.
Should it be configurable per user, per file, or even per rule
(timestamp with repeater)?
I am not familiar with RFC5545 iCalendar, so I am unsure what options it
recommends.
An example of recently designed library (however Org does not support
calendars with leap *months*):
<https://tc39.es/proposal-temporal/docs/calendar.html#handling-unusual-dates-leap-days-leap-months-and-skipped-or-repeated-periods>
"Handling unusual dates: leap days, leap months, and skipped or repeated
periods" (Temporal proposal for JavaScript)
> When Temporal encounters inputs representing a month and/or day that
> doesn't exist in the desired calendar year, by default (overridable in
> with or from via the overflow option) the inputs will be adjusted using
> the following algorithm:
>
> - First, pick the closest day in the same month. If there are two
> equally-close dates in that month, pick the later one.
> - If the month is a leap month that doesn't exist in the desired year,
> then pick another date according to the cultural conventions of that
> calendar's users. Usually this will result in the same day in the month
> before or the month after where that month would normally fall in a leap
> year.
> - Otherwise, pick the closest date to the provided date that is still in
> the same year. If there are two equally-close dates, pick the later one.
> - If the entire year doesn't exist, then pick the closest date to the
> provided date. If there are two equally-close dates, pick the later one.
next prev parent reply other threads:[~2024-04-06 14:53 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 10:48 Leap-year bug with todo-cycle Anton Haglund
2024-04-05 18:34 ` [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?) (was: Leap-year bug with todo-cycle) Ihor Radchenko
2024-04-05 19:53 ` Russell Adams
2024-04-05 21:18 ` jman
2024-04-05 21:27 ` Ihor Radchenko
2024-04-06 14:52 ` Max Nikulin [this message]
2024-04-07 11:47 ` [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?) Ihor Radchenko
2024-05-13 10:07 ` [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?) (was: Leap-year bug with todo-cycle) Ihor Radchenko
2024-05-14 11:08 ` [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?) Max Nikulin
2024-05-14 12:56 ` Ihor Radchenko
2024-05-14 13:10 ` Stefan Nobis
2024-05-18 11:40 ` Ihor Radchenko
2024-05-18 12:49 ` Stefan Nobis
2024-05-18 13:09 ` Ihor Radchenko
2024-05-18 14:26 ` Stefan Nobis
2024-05-18 14:35 ` Ihor Radchenko
2024-05-15 11:04 ` Max Nikulin
2024-05-18 11:50 ` Ihor Radchenko
2024-05-16 10:41 ` Max Nikulin
2024-05-18 11:56 ` Ihor Radchenko
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.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='uurnii$n7a$1@ciao.gmane.io' \
--to=manikulin@gmail.com \
--cc=emacs-orgmode@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/org-mode.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).