[-- Attachment #1: Type: text/plain, Size: 968 bytes --] Hi, In https://orgmode.org/manual/Deadlines-and-Scheduling.html#Deadlines-and-Scheduling 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. Thank you! Thanks, hhkg [-- Attachment #2: Type: text/html, Size: 1554 bytes --]
Hi,
hhkg@protonmail.com writes:
> In https://orgmode.org/manual/Deadlines-and-Scheduling.html#
> Deadlines-and-Scheduling
>
> 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.
Thanks,
--
Bastien
Hi,
hhkg@protonmail.com writes:
> 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.
Just bumping up this thread to confirm the bug is still there.
--
Bastien
i see the problem. but i get confused about the real-world purpose of this feature. is the idea that technically someplace in the real world you are supposed to work on it but you have decided not to and you don't want the agenda to show it until you will work on it? On 9/10/20, Bastien <bzg@gnu.org> wrote: > Hi, > > hhkg@protonmail.com writes: > >> 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. > > Just bumping up this thread to confirm the bug is still there. > > -- > Bastien > > -- The Kafka Pandemic Please learn what misopathy is. https://thekafkapandemic.blogspot.com/2013/10/why-some-diseases-are-wronged.html
Hi,
hhkg@protonmail.com writes:
> In https://orgmode.org/manual/Deadlines-and-Scheduling.html#
> Deadlines-and-Scheduling
>
> 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>.
I'm just bumping this thread because this issue is still open, I'll
review it before Org 9.5.
--
Bastien