From: Angel de Vicente <angel.vicente.garrido@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Timestamp with repeater interval AND END DATE?
Date: Tue, 31 May 2022 15:36:01 +0100 [thread overview]
Message-ID: <87bkvdg46m.fsf@gmail.com> (raw)
In-Reply-To: 87czfter3k.fsf@ucl.ac.uk
Hello,
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Tuesday, 31 May 2022 at 14:46, Angel de Vicente wrote:
>> Did I miss something in the manual?
>
> No, you did not miss anything. What you want cannot be done with a
> single time stamp. Instead, there are two alternatives:
>
> 1. use a diary s-exp (see info manual) which does allow this or
> 2. use org-clone-subtree-with-time-shift: create a single entry and then
> copy it as many times as desired.
in case it can be useful to somebody else, I ended up with an entry like
this, that does the job:
,----
| *** Badminton 20:45-22:15
| <%%(and (diary-cyclic 7 2022 05 30) (diary-block 2022 05 30 2022 06 30))>
`----
(the s-exp entry above assumes 'calendar-date-style' is set to 'iso')
Cheers,
--
Ángel de Vicente
Research Software Engineer (Supercomputing and BigData)
Instituto de Astrofísica de Canarias (https://www.iac.es/en)
next prev parent reply other threads:[~2022-05-31 14:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-31 13:46 Timestamp with repeater interval AND END DATE? Angel de Vicente
2022-05-31 14:03 ` Eric S Fraga
2022-05-31 14:36 ` Angel de Vicente [this message]
2022-06-10 8:44 ` Robert Pluim
2022-06-10 11:27 ` Angel de Vicente
2022-06-10 12:45 ` Robert Pluim
2022-06-10 12:59 ` Ihor Radchenko
2022-06-10 14:24 ` Robert Pluim
2022-06-10 15:03 ` Ihor Radchenko
2022-06-10 15:59 ` Robert Pluim
2022-06-11 4:51 ` Ihor Radchenko
2022-06-10 14:37 ` Ambiguity in commit message conventions for org Robert Pluim
2022-06-10 15:11 ` Ihor Radchenko
2022-06-10 16:02 ` Robert Pluim
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=87bkvdg46m.fsf@gmail.com \
--to=angel.vicente.garrido@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).