* [feature] Handle recurrence in <> and [] dates
@ 2018-10-22 16:58 Leo Gaspard
2018-11-06 12:34 ` Leo Gaspard
0 siblings, 1 reply; 9+ messages in thread
From: Leo Gaspard @ 2018-10-22 16:58 UTC (permalink / raw)
To: emacs-orgmode
Hello all!
I have been using org-mode for a few days (switching over from
todo.txt [1]), and for the time being my experience has been great!
There is a single thing I found weird up to now: it seems that
recurrence tags in <> and [] “tags” don't get bumped when a task is
completed and has a recurrence set in its SCHEDULED or DEADLINE date.
The reason I'd like this is because I have monthly bank statements,
which come in the next month, and I'd like to store the bank statement's
date in a [] “tag” so that I can easily know which statement I'm
supposed to handle, even though this date is neither a SCHEDULED (as I
don't have the statement yet at the date it's produced) nor a DEADLINE
(for the same reason).
What do you think about this?
Anyway, thanks a lot for the great work!
Cheers,
Leo
[1] http://todotxt.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [feature] Handle recurrence in <> and [] dates
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
0 siblings, 1 reply; 9+ messages in thread
From: Leo Gaspard @ 2018-11-06 12:34 UTC (permalink / raw)
To: emacs-orgmode
Hello all!
It's been ~2 weeks so I hope you'll forgive me bumping my post :)
Do you have an opinion about this idea?
Cheers,
Leo
Leo Gaspard <orgmode@leo.gaspard.io> writes:
> Hello all!
>
> I have been using org-mode for a few days (switching over from
> todo.txt [1]), and for the time being my experience has been great!
>
> There is a single thing I found weird up to now: it seems that
> recurrence tags in <> and [] “tags” don't get bumped when a task is
> completed and has a recurrence set in its SCHEDULED or DEADLINE date.
>
> The reason I'd like this is because I have monthly bank statements,
> which come in the next month, and I'd like to store the bank statement's
> date in a [] “tag” so that I can easily know which statement I'm
> supposed to handle, even though this date is neither a SCHEDULED (as I
> don't have the statement yet at the date it's produced) nor a DEADLINE
> (for the same reason).
>
> What do you think about this?
>
> Anyway, thanks a lot for the great work!
>
> Cheers,
> Leo
>
>
> [1] http://todotxt.org/
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [feature] Handle recurrence in <> and [] dates
2018-11-06 12:34 ` Leo Gaspard
@ 2018-11-06 13:15 ` Julius Dittmar
2018-11-06 14:36 ` Leo Gaspard
0 siblings, 1 reply; 9+ messages in thread
From: Julius Dittmar @ 2018-11-06 13:15 UTC (permalink / raw)
To: emacs-orgmode
Hi Leo,
if you want a task to re-open at a later date upon closing, add a line of
:REPEAT_TO_STATE: TODO
to the PROPERTIES drawer of that task.
Hth,
Julius
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [feature] Handle recurrence in <> and [] dates
2018-11-06 13:15 ` Julius Dittmar
@ 2018-11-06 14:36 ` Leo Gaspard
2018-11-10 19:01 ` Nicolas Goaziou
0 siblings, 1 reply; 9+ messages in thread
From: Leo Gaspard @ 2018-11-06 14:36 UTC (permalink / raw)
To: Julius Dittmar, emacs-orgmode
Hi Julius,
Julius Dittmar <Julius.Dittmar@gmx.de> writes:
> if you want a task to re-open at a later date upon closing, add a line of
> :REPEAT_TO_STATE: TODO
> to the PROPERTIES drawer of that task.
Well, I guess I stated my problem poorly, sorry :)
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.
Is there a trick to do this?
Cheers,
Leo
^ permalink raw reply [flat|nested] 9+ messages in thread* Re: [feature] Handle recurrence in <> and [] dates
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
0 siblings, 2 replies; 9+ messages in thread
From: Nicolas Goaziou @ 2018-11-10 19:01 UTC (permalink / raw)
To: Leo Gaspard; +Cc: Julius Dittmar, emacs-orgmode
Hello,
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.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [feature] Handle recurrence in <> and [] dates
2018-11-10 19:01 ` Nicolas Goaziou
@ 2018-11-11 3:27 ` Leo Gaspard
2018-11-14 15:29 ` Marco Wahl
1 sibling, 0 replies; 9+ messages in thread
From: Leo Gaspard @ 2018-11-11 3:27 UTC (permalink / raw)
To: Nicolas Goaziou; +Cc: Julius Dittmar, emacs-orgmode
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Org didn't handle repeaters in inactive time stamps. This is now fixed
> (in master). Thank you.
Great, thank you!
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [feature] Handle recurrence in <> and [] dates
2018-11-10 19:01 ` Nicolas Goaziou
2018-11-11 3:27 ` Leo Gaspard
@ 2018-11-14 15:29 ` Marco Wahl
2018-11-17 15:35 ` Nicolas Goaziou
1 sibling, 1 reply; 9+ messages in thread
From: Marco Wahl @ 2018-11-14 15:29 UTC (permalink / raw)
To: emacs-orgmode
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
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [feature] Handle recurrence in <> and [] dates
2018-11-14 15:29 ` Marco Wahl
@ 2018-11-17 15:35 ` Nicolas Goaziou
2018-11-17 19:46 ` Marco Wahl
0 siblings, 1 reply; 9+ messages in thread
From: Nicolas Goaziou @ 2018-11-17 15:35 UTC (permalink / raw)
To: Marco Wahl; +Cc: emacs-orgmode
Hello,
Marco Wahl <marcowahlsoft@gmail.com> writes:
> 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.
I think it should now be fixed in master. Could you confirm it?
Thank you.
Regards,
--
Nicolas Goaziou
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [feature] Handle recurrence in <> and [] dates
2018-11-17 15:35 ` Nicolas Goaziou
@ 2018-11-17 19:46 ` Marco Wahl
0 siblings, 0 replies; 9+ messages in thread
From: Marco Wahl @ 2018-11-17 19:46 UTC (permalink / raw)
To: emacs-orgmode
>> 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.
>
> I think it should now be fixed in master. Could you confirm it?
Looks fine to me! Thanks!
Ciao,
--
Marco
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2018-11-17 19:47 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
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
2018-11-17 15:35 ` Nicolas Goaziou
2018-11-17 19:46 ` Marco Wahl
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).