emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: hhkg@protonmail.com
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Delay all occurences for a heading scheduled with repeater not work.
Date: Tue, 04 May 2021 00:33:42 +0200	[thread overview]
Message-ID: <87o8dr30s9.fsf@gnu.org> (raw)
In-Reply-To: <JGtL5M2BLJxLqyCt4F86F3jag6au9ImpBLpjan8mqliIBVvuVNnEjvtFcpDUopcep8t4Jh7HxsAefXfcHflsVjscQZBgKWa8A0rPLbiTOsE=@protonmail.com> (hhkg@protonmail.com's message of "Thu, 30 Jan 2020 16:24:32 +0000")

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


      parent reply	other threads:[~2021-05-03 22:57 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-30 16:24 Delay all occurences for a heading scheduled with repeater not work hhkg
2020-02-01  8:47 ` Bastien
2020-09-10 12:20 ` Bastien
2020-09-10 22:40   ` Samuel Wales
2021-05-03 22:33 ` Bastien [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

  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=87o8dr30s9.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=hhkg@protonmail.com \
    /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).