all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Michael Heerdegen <michael_heerdegen@web.de>
To: "Renaud Bussières via General discussions about Org-mode."
	<emacs-orgmode@gnu.org>
Cc: "Renaud Bussières" <contact@renaudbussieres.com>
Subject: Re: What's the proper way to define a recurring event
Date: Tue, 17 Dec 2024 18:21:31 +0100	[thread overview]
Message-ID: <878qseteck.fsf@web.de> (raw)
In-Reply-To: <87bjxe2lwa.fsf@renaudbussieres.com> ("Renaud Bussières via \"General discussions about Org-mode.\""'s message of "Sat, 14 Dec 2024 12:51:33 -0500")

Renaud Bussières via "General discussions about Org-mode."
<emacs-orgmode@gnu.org> writes:

> <2024-10-07 Mon 16:00-17:30 +1w>--<2024-11-25 Mon>
>
> Then the event will appear in the agenda every day between 2024-10-07
> and 2024-11-25, that's not right. It seems like time/date ranges do
> not respect repeaters.

I can't estimate whether the syntax of org time specs could or should be
extended like that.  But as a workaround - or even as equally good
alternative - you can use diary sexps, which are able to express any
possible conditions.

For me (I am using calendar-set-date-style --> european with day and
month positions switched) your example would look like

** 16:00-17:30 Yoga
%%(and (diary-cyclic 7 7 10 2024)
       (diary-block 7 10 2024 25 11 2024)
       "16:00-17:30 Yoga Class")

Note: the entry name is taken from the return value of the expression,
the actual entry name is ignored, at least for the agenda.


Michael.


      parent reply	other threads:[~2024-12-17 17:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-14 17:51 What's the proper way to define a recurring event Renaud Bussières via General discussions about Org-mode.
2024-12-14 18:15 ` Mark Barton
2024-12-17 17:21 ` Michael Heerdegen [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

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

  git send-email \
    --in-reply-to=878qseteck.fsf@web.de \
    --to=michael_heerdegen@web.de \
    --cc=contact@renaudbussieres.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 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.