From: Bastien <firstname.lastname@example.org>
Cc: "email@example.com" <firstname.lastname@example.org>
Subject: Re: Delay all occurences for a heading scheduled with repeater not work.
Date: Sat, 01 Feb 2020 09:47:08 +0100 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: <JGtL5M2BLJxLqyCt4F86F3jag6au9ImpBLpjan8mqliIBVvuVNnEjvtFcpDUopcep8t4Jh7HxsAefXfcHflsVjscQZBgKWa8A0rPLbiTOsEfirstname.lastname@example.org> (email@example.com's message of "Thu, 30 Jan 2020 16:24:32 +0000")
> In https://orgmode.org/manual/Deadlines-and-Scheduling.html#
> It says:
> "If you want to delay the display of this task in the agenda, use
> ‘SCHEDULED: <2004-12-25 Sat -2d>’: the task is still scheduled on the
> 25th but will appear two days later. In case the task contains a
> repeater, the delay is considered to affect all occurrences; if you
> want the delay to only affect the first scheduled occurrence of the
> task, use ‘--2d’ instead."
> With headings below:
> * delay in scheduled with repeater
> ** TODO delay all occurences
> SCHEDULED: <2020-01-30 Thu -1d +2d>
> ** TODO delay only the first occurence
> SCHEDULED: <2020-01-30 Thu --1d +2d>
> Both headings display in today's agenda (today is <2020-01-31>).
> Which is correct.
> Then both display in agenda of <2020-02-01>.
> Which is not correct for 'delay all occurences'.
> It should display in agenda of <2020-02-02>.
> Please help check if this should be fixed.
Yes, this should be fixed and this is now fixed in the maint branch,
it will be part of the next bugfix (if any) or major release.
This was quite tricky to solve, please test it carefully.
next prev parent reply other threads:[~2020-02-01 8:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 16:24 hhkg
2020-02-01 8:47 ` Bastien [this message]
2020-09-10 12:20 ` Bastien
2020-09-10 22:40 ` Samuel Wales
2021-05-03 22:33 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).