Recurring todos gets closed and not re-scheduled

Recurring todos gets closed and not re-scheduled

[Karl Voit]

Hi!

I recently updated Org to d85ff34086e5398b7c83cf66694f3f7d09695ce8
(git).

When I mark following recurring todos as done, all of them gets
marked as DONE and CLOSED.

,----[ examples before being marked as DONE ]
| *** NEXT Test task with scheduled
| SCHEDULED: <2016-01-17 Sun +1w>
| :PROPERTIES:
| :CREATED:  [2016-01-15 Fri 15:06]
| :END:
|
| *** NEXT Test task with deadline
| DEADLINE: <2016-01-17 Sun +1w>
| :PROPERTIES:
| :CREATED:  [2016-01-15 Fri 15:06]
| :END:
|
| *** NEXT Test task with scheduled + deadline
| DEADLINE: <2016-01-17 Sun +1w> SCHEDULED: <2016-01-17 Sun +1w>
| :PROPERTIES:
| :CREATED:  [2016-01-15 Fri 15:07]
| :END:
`----

,----[ examples after being marked as DONE ]
| *** DONE Test task with scheduled
| CLOSED: [2016-01-15 Fri 15:15] SCHEDULED: <2016-01-17 Sun +1w>
| :PROPERTIES:
| :CREATED:  [2016-01-15 Fri 15:06]
| :END:
| :LOGBOOK:
| - State "DONE"       from "NEXT"       [2016-01-15 Fri 15:15]
| :END:
|
| *** DONE Test task with deadline
| CLOSED: [2016-01-15 Fri 15:15] DEADLINE: <2016-01-17 Sun +1w>
| :PROPERTIES:
| :CREATED:  [2016-01-15 Fri 15:06]
| :END:
| :LOGBOOK:
| - State "DONE"       from "NEXT"       [2016-01-15 Fri 15:15]
| :END:
|
| *** DONE Test task with scheduled + deadline
| CLOSED: [2016-01-15 Fri 15:15] DEADLINE: <2016-01-17 Sun +1w> SCHEDULED: <2016-01-17 Sun +1w>
| :PROPERTIES:
| :CREATED:  [2016-01-15 Fri 15:07]
| :END:
| :LOGBOOK:
| - State "DONE"       from "NEXT"       [2016-01-15 Fri 15:15]
| :END:
`----

The previous behavior was different: recurring todos got
re-scheduled for the next iteration. I need this behavior back
otherwise recurring todos are of no use to me.

I found in ORG-NEWS:

,----
| *** Clear non-repeated SCHEDULED upon repeating a task
| If the task is repeated, and therefore done at least one, scheduling
| information is no longer relevant.  It is therefore removed.
`----

... with reference to [1]

Does my issue relate to this change? Is it a bug? Do I have to
modify my settings?

Thanks!


[1] http://orgmode.org/cgit.cgi/org-mode.git/commit/?id=481719fbd5751aaa9c672b762cb43aea8ee986b0


-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: Recurring todos gets closed and not re-scheduled

[Marco Wahl]

Hi!

Karl Voit <devnull@Karl-Voit.at> writes:

> I recently updated Org to d85ff34086e5398b7c83cf66694f3f7d09695ce8
> (git).
>
> When I mark following recurring todos as done, all of them gets
> marked as DONE and CLOSED.
>
> ,----[ examples before being marked as DONE ]
> | *** NEXT Test task with scheduled
> | SCHEDULED: <2016-01-17 Sun +1w>
> | :PROPERTIES:
> | :CREATED:  [2016-01-15 Fri 15:06]
> | :END:
> |
> | *** NEXT Test task with deadline

[...]

>
> ,----[ examples after being marked as DONE ]
> | *** DONE Test task with scheduled
> | CLOSED: [2016-01-15 Fri 15:15] SCHEDULED: <2016-01-17 Sun +1w>
> | :PROPERTIES:
> | :CREATED:  [2016-01-15 Fri 15:06]
> | :END:
> | :LOGBOOK:
> | - State "DONE"       from "NEXT"       [2016-01-15 Fri 15:15]
> | :END:
> |
> | *** DONE Test task with deadline

[...]

> The previous behavior was different: recurring todos got
> re-scheduled for the next iteration. I need this behavior back
> otherwise recurring todos are of no use to me.

[...]

Possibly you faced the same issue as stated in
http://permalink.gmane.org/gmane.emacs.orgmode/104179.

This issue is fixed in the current git-version AFAICT.  It was an issue
with the change to lexical-scoping.  I recommend you to try the new
version.


Bye,
-- 
Marco Wahl
GPG: 0x49010A040A3AE6F2

Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated (was: Recurring todos gets closed and not re-scheduled)

[Karl Voit]

Hi Marco!

* Marco Wahl <marcowahlsoft@gmail.com> wrote:
> Hi!
>
> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> I recently updated Org to d85ff34086e5398b7c83cf66694f3f7d09695ce8
>> (git).
>>
>> When I mark following recurring todos as done, all of them gets
>> marked as DONE and CLOSED.
>>
>> ,----[ examples before being marked as DONE ]
>> | *** NEXT Test task with scheduled
>> | SCHEDULED: <2016-01-17 Sun +1w>
>> | :PROPERTIES:
>> | :CREATED:  [2016-01-15 Fri 15:06]
>> | :END:
>> |
>> | *** NEXT Test task with deadline
>
> [...]
>
>> ,----[ examples after being marked as DONE ]
>> | *** DONE Test task with scheduled
>> | CLOSED: [2016-01-15 Fri 15:15] SCHEDULED: <2016-01-17 Sun +1w>
>> | :PROPERTIES:
>> | :CREATED:  [2016-01-15 Fri 15:06]
>> | :END:
>> | :LOGBOOK:
>> | - State "DONE"       from "NEXT"       [2016-01-15 Fri 15:15]
>> | :END:
>> |
>> | *** DONE Test task with deadline
>
> [...]
>
>> The previous behavior was different: recurring todos got
>> re-scheduled for the next iteration. I need this behavior back
>> otherwise recurring todos are of no use to me.
>
> [...]
>
> Possibly you faced the same issue as stated in
> http://permalink.gmane.org/gmane.emacs.orgmode/104179.
>
> This issue is fixed in the current git-version AFAICT.  It was an issue
> with the change to lexical-scoping.  I recommend you to try the new
> version.

Thanks for your pointer.

I upgraded to the most current git version and this issue is gone.
Thanks very much!

Unfortunately, this fix (or any other commit?) prevents my
non-recurring tasks to be completed when I got "DEADLINE" or
"SCHEDULED" in the body text within blocks or comments.

So I guess the new scope is too generous.

It's an edge-case but it should be fixed. When I do mark the following three
example headers as done ...

    *** NEXT test with quote

    #+BEGIN_QUOTE
    ,----[ examples ]
    | DEADLINE: <2016-01-31 Sun +1w>
    `----
    #+END_QUOTE

    *** NEXT test with example

    #+BEGIN_EXAMPLE
    ,----[ examples ]
    | DEADLINE: <2016-01-31 Sun +1w>
    `----
    #+END_EXAMPLE

    *** NEXT test with :

    : ,----[ examples ]
    : | DEADLINE: <2016-01-31 Sun +1w>
    : `----

... I get:

    *** NEXT test with quote
    :PROPERTIES:
    :CREATED:  [2016-01-17 Sun 10:36]
    :LAST_REPEAT: [2016-01-17 Sun 10:36]
    :END:
    :LOGBOOK:
    - State "DONE"       from "NEXT"       [2016-01-17 Sun 10:36]
    :END:
    
    #+BEGIN_QUOTE
    ,----[ examples ]
    | DEADLINE: <2016-02-07 Sun +1w>
    `----
    #+END_QUOTE
    
    *** NEXT test with example
    :PROPERTIES:
    :CREATED:  [2016-01-17 Sun 10:36]
    :LAST_REPEAT: [2016-01-17 Sun 10:36]
    :END:
    :LOGBOOK:
    - State "DONE"       from "NEXT"       [2016-01-17 Sun 10:36]
    :END:
    
    #+BEGIN_EXAMPLE
    ,----[ examples ]
    | DEADLINE: <2016-02-07 Sun +1w>
    `----
    #+END_EXAMPLE
    
    *** NEXT test with :
    :PROPERTIES:
    :CREATED:  [2016-01-17 Sun 10:36]
    :LAST_REPEAT: [2016-01-17 Sun 10:36]
    :END:
    :LOGBOOK:
    - State "DONE"       from "NEXT"       [2016-01-17 Sun 10:36]
    :END:
    
    : ,----[ examples ]
    : | DEADLINE: <2016-02-07 Sun +1w>
    : `----


-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github

Re: Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated

[Marco Wahl]

Hi Karl!

>> Karl Voit <devnull@Karl-Voit.at> writes:

[...]

> Unfortunately, this fix (or any other commit?) prevents my
> non-recurring tasks to be completed when I got "DEADLINE" or
> "SCHEDULED" in the body text within blocks or comments.

> It's an edge-case but it should be fixed. When I do mark the following three
> example headers as done ...
>
>     *** NEXT test with quote
>
>     #+BEGIN_QUOTE
>     ,----[ examples ]
>     | DEADLINE: <2016-01-31 Sun +1w>
>     `----
>     #+END_QUOTE
>
>
>     *** NEXT test with example
>
>     #+BEGIN_EXAMPLE
>     ,----[ examples ]
>     | DEADLINE: <2016-01-31 Sun +1w>
>     `----
>     #+END_EXAMPLE
>
>
>     *** NEXT test with :
>
>     : ,----[ examples ]
>     : | DEADLINE: <2016-01-31 Sun +1w>
>     : `----

I can reproduce your statement.  Even the subtree containing just a
repeater without string DEADLINE or SCHEDULED does not get completed.

--8<---------------cut here---------------start------------->8---

* TODO Thing

#+BEGIN_QUOTE
<2016-01-01 Sun +1w>
#+END_QUOTE

--8<---------------cut here---------------end--------------->8---

I agree with you that this behavior is unfortunate.

AFAICS there is nothing yet in the documentation about this case.  This
means we can define a behavior.  What about the requirement:

Do neither touch nor take into account any date contained in any block
of an item for progressing the item.

I think this requirement could be discussed, corrected, refined and
finally be implemented.

Meanwhile you need to take care of such items and rewrite the todo
keyword manually.  Org files are still text files. ;)

BTW the documentation of `org-todo' has: "With a numeric prefix arg of
-1, cancel repeater to allow marking as DONE."

> So I guess the new scope is too generous.

I bet that this issue has been there all the time.


Best regards,
-- 
Marco Wahl
GPG: 0x49010A040A3AE6F2

Re: Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated

[Rasmus]

Karl Voit <devnull@Karl-Voit.at> writes:

> Unfortunately, this fix (or any other commit?) prevents my
> non-recurring tasks to be completed when I got "DEADLINE" or
> "SCHEDULED" in the body text within blocks or comments.

Isn't this the this feature?  The Org syntax¹ specifies:

     A planning is an element with the following pattern:

         HEADLINE
         PLANNING

     where HEADLINE is a headline element and PLANNING is a line filled with
     INFO parts, where each of them follows the pattern:

         KEYWORD: TIMESTAMP

     KEYWORD is either “DEADLINE”, “SCHEDULED” or “CLOSED”. TIMESTAMP is a
     timestamp object.

     In particular, no blank line is allowed between PLANNING and HEADLINE.

Rasmus


Footnotes: 
¹   http://orgmode.org/worg/dev/org-syntax.html#Clock,_Diary_Sexp_and_Planning

-- 
Look, it is what it is because of what it was

Re: Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated

[Marco Wahl]

Rasmus <rasmus@gmx.us> writes:

> Karl Voit <devnull@Karl-Voit.at> writes:
>
>> Unfortunately, this fix (or any other commit?) prevents my
>> non-recurring tasks to be completed when I got "DEADLINE" or
>> "SCHEDULED" in the body text within blocks or comments.
>
> Isn't this the this feature?  The Org syntax¹ specifies:
> Footnotes: 
> ¹   http://orgmode.org/worg/dev/org-syntax.html#Clock,_Diary_Sexp_and_Planning

IIUC the issue here is solely for dates contained within a block.

The behavior of Org for those dates (in particular when a repeater like
'+1w' is involved) on progressing the todo is unspecified AFAICS.


Best regards,
-- 
Marco Wahl
GPG: 0x49010A040A3AE6F2

Re: Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated

[Nicolas Goaziou]

Hello,

Karl Voit <devnull@Karl-Voit.at> writes:

> Unfortunately, this fix (or any other commit?) prevents my
> non-recurring tasks to be completed when I got "DEADLINE" or
> "SCHEDULED" in the body text within blocks or comments.
>
> So I guess the new scope is too generous.
>
> It's an edge-case but it should be fixed. When I do mark the following three
> example headers as done ...
>
>     *** NEXT test with quote
>
>     #+BEGIN_QUOTE
>     ,----[ examples ]
>     | DEADLINE: <2016-01-31 Sun +1w>
>     `----
>     #+END_QUOTE
>
>     *** NEXT test with example
>
>     #+BEGIN_EXAMPLE
>     ,----[ examples ]
>     | DEADLINE: <2016-01-31 Sun +1w>
>     `----
>     #+END_EXAMPLE
>
>     *** NEXT test with :
>
>     : ,----[ examples ]
>     : | DEADLINE: <2016-01-31 Sun +1w>
>     : `----
>
> ... I get:
>
>     *** NEXT test with quote
>     :PROPERTIES:
>     :CREATED:  [2016-01-17 Sun 10:36]
>     :LAST_REPEAT: [2016-01-17 Sun 10:36]
>     :END:
>     :LOGBOOK:
>     - State "DONE"       from "NEXT"       [2016-01-17 Sun 10:36]
>     :END:
>     
>     #+BEGIN_QUOTE
>     ,----[ examples ]
>     | DEADLINE: <2016-02-07 Sun +1w>
>     `----
>     #+END_QUOTE
>     
>     *** NEXT test with example
>     :PROPERTIES:
>     :CREATED:  [2016-01-17 Sun 10:36]
>     :LAST_REPEAT: [2016-01-17 Sun 10:36]
>     :END:
>     :LOGBOOK:
>     - State "DONE"       from "NEXT"       [2016-01-17 Sun 10:36]
>     :END:
>     
>     #+BEGIN_EXAMPLE
>     ,----[ examples ]
>     | DEADLINE: <2016-02-07 Sun +1w>
>     `----
>     #+END_EXAMPLE
>     
>     *** NEXT test with :
>     :PROPERTIES:
>     :CREATED:  [2016-01-17 Sun 10:36]
>     :LAST_REPEAT: [2016-01-17 Sun 10:36]
>     :END:
>     :LOGBOOK:
>     - State "DONE"       from "NEXT"       [2016-01-17 Sun 10:36]
>     :END:
>     
>     : ,----[ examples ]
>     : | DEADLINE: <2016-02-07 Sun +1w>
>     : `----

Fixed (in master only). Thank you.


Regards,

-- 
Nicolas Goaziou

Re: Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated

[Karl Voit]

* Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
> Hello,

Hi!

> Fixed (in master only). Thank you.

Thank you very much!

-- 
mail|git|SVN|photos|postings|SMS|phonecalls|RSS|CSV|XML to Org-mode:
       > get Memacs from https://github.com/novoid/Memacs <

https://github.com/novoid/extract_pdf_annotations_to_orgmode + more on github