emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Moakt Temporary Email <097073ee6adb@drmail.in>
Cc: emacs-orgmode@gnu.org
Subject: Re: [orgmode] Better recurrence for SCHEDULED and DEADLINE
Date: Mon, 19 Aug 2024 08:52:03 +0000	[thread overview]
Message-ID: <87sev07v4c.fsf@localhost> (raw)
In-Reply-To: <A6aKpYU75RsF8LccZUVeiOCtThKcAv7ovlbIduqz48@localhost.localdomain>

Moakt Temporary Email <097073ee6adb@drmail.in> writes:

>>That would indeed be nice. But may you provide more details on how you
>>envision such support to be implemented?
>
> ...
> "++1m@Mon#1"? Maybe employ cron syntax for month and week for what's after "@"? Another example: "++1m@17" (= add 1 month then the next 17th of the month)

Note that we also have diary style timestamps with arbitrary logic of
date selection.

The question is whether a more specialized repeater specification is
needed. And if it is needed, what should be the available features.

So far, you listed:
1. Specific day of week, nth from the beginning of month
2. "add 1 month then the next 17th of the month" - I do not
   understand. How is it different from <2024-08-17 ++1m>?

-- 
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>


  reply	other threads:[~2024-08-19  9:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-18 12:05 [orgmode] Better recurrence for SCHEDULED and DEADLINE Moakt Temporary Email
2024-08-19  8:52 ` Ihor Radchenko [this message]
2024-08-19 17:40   ` Milan Zamazal
2024-08-19 21:53     ` Rudolf Adamkovič
2024-08-20  4:39       ` Ihor Radchenko
2024-08-20 18:35     ` Ihor Radchenko
  -- strict thread matches above, loose matches on Subject: below --
2024-08-21 11:59 Moakt Temporary Email
2024-08-19  9:35 Moakt Temporary Email
2024-08-17 12:31 Moakt Temporary Email
2024-08-18 10:41 ` 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=87sev07v4c.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=097073ee6adb@drmail.in \
    --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).