From: Marco Wahl <marcowahlsoft@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: [feature] Handle recurrence in <> and [] dates
Date: Wed, 14 Nov 2018 16:29:40 +0100 [thread overview]
Message-ID: <848t1vllsr.fsf@gmail.com> (raw)
In-Reply-To: 87muqgbvus.fsf@nicolasgoaziou.fr
Hi!
> Leo Gaspard <orgmode@leo.gaspard.io> writes:
>
>> Here is a translated example task from my .org file:
>>
>> *** TODO Check bank report
>> SCHEDULED: <2000-02-10 Thu +1m>
>>
>> Dated [2000-01-01 Sat +1m]
>>
>> The point of this “Dated” field being to tell me to which report I
>> should be looking, given I sometimes am a month late or so in checking
>> my reports, and just put them in the (physical) drawer as I receive
>> them.
>>
>> This “Dated” field is exactly what I would like to see updated when I
>> mark the task as done (like the SCHEDULED date), but it looks like it
>> doesn't move.
>
> Org didn't handle repeaters in inactive time stamps. This is now fixed
> (in master). Thank you.
AFAICT the performance of marking tasks done which contain *a lot* of
inactive timestams has degraded considerably with this change.
Example:
#v+
* TODO task
SCHEDULED: <2018-11-15 .+1d>
:PROPERTIES:
:STYLE: habit
:LAST_REPEAT: [2018-11-14 16:26]
:END:
[2018-07-10 Tue 11:29]--[2018-07-10 Tue 12:10]
[2018-07-09 Mon 15:20]--[2018-07-09 Mon 15:23]
[2018-07-08 Sun 09:01]--[2018-07-08 Sun 09:20]
...
<hundreds of these lines>
...
[2013-07-08 Sun 09:01]--[2013-07-08 Sun 09:20]
#v-
Sorry for not having digged deeper into this issue yet.
Ciao, Marco
next prev parent reply other threads:[~2018-11-14 15:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-22 16:58 [feature] Handle recurrence in <> and [] dates Leo Gaspard
2018-11-06 12:34 ` Leo Gaspard
2018-11-06 13:15 ` Julius Dittmar
2018-11-06 14:36 ` Leo Gaspard
2018-11-10 19:01 ` Nicolas Goaziou
2018-11-11 3:27 ` Leo Gaspard
2018-11-14 15:29 ` Marco Wahl [this message]
2018-11-17 15:35 ` Nicolas Goaziou
2018-11-17 19:46 ` Marco Wahl
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=848t1vllsr.fsf@gmail.com \
--to=marcowahlsoft@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).