From: "J. G." <jerzor@pacbell.net>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: Orgmode <emacs-orgmode@gnu.org>
Subject: Re: [BUG] Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization
Date: Thu, 27 Apr 2023 15:24:39 +0000 (UTC) [thread overview]
Message-ID: <256094831.903620.1682609079969@mail.yahoo.com> (raw)
In-Reply-To: <87ildho952.fsf@localhost>
[-- Attachment #1: Type: text/plain, Size: 1960 bytes --]
Thanks for confirming the issue.
For the record, after doing some more research it looks like at least one other person came across this issue, and the workaround was using org-edna in place of the repeaters, which will push the timestamps together to the same date offset prior to the scheduled-deadline date range, and then increment them forward to the correct dates:
Use Edna Instead of the Repeater Pattern · Konubinix' Site
|
|
| |
Use Edna Instead of the Repeater Pattern · Konubinix' Site
|
|
|
On Thursday, April 27, 2023 at 04:28:11 AM PDT, Ihor Radchenko <yantar92@posteo.net> wrote:
"J. G." <jerzor@pacbell.net> writes:
> * TODO My late recurring todoSCHEDULED: <2023-04-12 Wed ++1w> DEADLINE: <2023-04-13 Thu ++1w>
> Right now it is Wednesday (2023-04-26 to be precise), and as shown above, my task had a scheduled timestamp on a Wednesday from a previous week. The repeater is ++1w, so marking the task as done bumps it to repeat on Wednesday of next week (2023-05-03 to be precise). That functions as expected.
> But the deadline timestamp is on a Thursday of a previous week with a
> repeater of ++1w, so marking the task as done bumps it to Thursday of
> this week (2023-04-27 to be precise). So marking it as done it has the
> logical but unexpected result of having the scheduled timestamp for a
> date (2023-05-03) after the deadline timestamp (2023-04-27).
Confirmed.
I think it makes sense to have a special case for scheduled and
deadlines, making sure that they shift by the same number of days in
future, when their repeaters are the same.
However, I do not think that it should be done for all other timestamps
under heading.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
[-- Attachment #2: Type: text/html, Size: 6163 bytes --]
prev parent reply other threads:[~2023-04-27 15:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1032532251.385739.1682523845362.ref@mail.yahoo.com>
2023-04-26 15:44 ` Linking SCHEDULED and DEADLINE repeating timestamps to avoid desynchronization J. G.
2023-04-27 11:30 ` [BUG] " Ihor Radchenko
2023-04-27 15:24 ` J. G. [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=256094831.903620.1682609079969@mail.yahoo.com \
--to=jerzor@pacbell.net \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).