Re: [POLL] Dealing with +1m/y repeaters when jumping to impossible date (should 05-31 +1m be 07-01 or 06-30?)

[Ihor Radchenko <yantar92@posteo.net>]

Stefan Nobis <stefan-ml@snobis.de> writes:

> ...
> And even if we would have access to the original date: It may be
> something like the last day of February and from that alone it is not
> evident, wether e.g. the 28. of each month should be used or the last
> day of month.
>
> Therefore, I think, the only solution to this problem is to have some
> kind of special 'last day of month' marker. Maybe something like
> "+1m!" or any other way of encoding this "go to the last day of the
> next month" directly into the increment specifier.

+1m! is awkward - what if [2024-05-12 +1m!]?

One option might be something like [2024-05--1 +1m] that will work
nicely with glibc's time rounding conventions:

(format-time-string "%Y-%m-%d" (encode-time '(0 0 0 -1 5 2024))) ; => 2024-04-29

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>