From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rasmus Subject: Re: Scope issue: "SCHEDULED/DEADLINE" in blocks are being evaluated Date: Sun, 17 Jan 2016 13:57:27 +0100 Message-ID: <87mvs48itk.fsf@gmx.us> References: <2016-01-15T15-10-01@devnull.Karl-Voit.at> <84mvs6c1b4.fsf@gmail.com> <2016-01-17T10-09-57@devnull.Karl-Voit.at> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:48830) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aKmto-00041j-Vw for emacs-orgmode@gnu.org; Sun, 17 Jan 2016 07:57:41 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aKmtl-0006Ox-0K for emacs-orgmode@gnu.org; Sun, 17 Jan 2016 07:57:40 -0500 Received: from plane.gmane.org ([80.91.229.3]:46753) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aKmtk-0006On-PO for emacs-orgmode@gnu.org; Sun, 17 Jan 2016 07:57:36 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1aKmth-0004DA-QJ for emacs-orgmode@gnu.org; Sun, 17 Jan 2016 13:57:33 +0100 Received: from tsn109-201-154-186.dyn.nltelcom.net ([109.201.154.186]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Jan 2016 13:57:33 +0100 Received: from rasmus by tsn109-201-154-186.dyn.nltelcom.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sun, 17 Jan 2016 13:57:33 +0100 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org 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 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