From: Karl Voit <devnull@Karl-Voit.at>
To: emacs-orgmode@gnu.org
Subject: Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated (was: Recurring todos gets closed and not re-scheduled)
Date: Sun, 17 Jan 2016 10:38:05 +0100 [thread overview]
Message-ID: <2016-01-17T10-09-57@devnull.Karl-Voit.at> (raw)
In-Reply-To: 84mvs6c1b4.fsf@gmail.com
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
next prev parent reply other threads:[~2016-01-17 9:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-15 14:19 Recurring todos gets closed and not re-scheduled Karl Voit
2016-01-15 15:25 ` Marco Wahl
2016-01-17 9:38 ` Karl Voit [this message]
2016-01-17 12:33 ` Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated Marco Wahl
2016-01-17 12:57 ` Rasmus
2016-01-17 13:53 ` Marco Wahl
2016-01-17 21:24 ` Nicolas Goaziou
2016-01-18 14:07 ` Karl Voit
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2016-01-17T10-09-57@devnull.Karl-Voit.at \
--to=devnull@karl-voit.at \
--cc=emacs-orgmode@gnu.org \
--cc=news1142@Karl-Voit.at \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.