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

* Nicolas Goaziou 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 <

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

Hello, Karl Voit 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

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

Hi Marco! * Marco Wahl wrote: > Hi! > > Karl Voit 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. >> >>

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

Hi Karl! >> Karl Voit 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

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

Karl Voit 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

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

Rasmus writes: > Karl Voit 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?