From mboxrd@z Thu Jan  1 00:00:00 1970
From: Rainer Stengele <rainer.stengele@online.de>
Subject: Re: DEADLINE ignored?
Date: Thu, 14 Dec 2017 11:59:24 +0100
Message-ID: <813df7d1-1275-97c8-6f72-200b99f99b1b@online.de>
References: <d3b1a61d-9cf2-6dfa-fbeb-45fb7bbe88e8@gmail.com>
	<87fuc2ahmn.fsf@pinto.chemeng.ucl.ac.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:56578)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <rainer.stengele@online.de>) id 1ePREt-0002ix-9f
	for emacs-orgmode@gnu.org; Thu, 14 Dec 2017 05:59:50 -0500
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <rainer.stengele@online.de>) id 1ePREb-0000uD-8r
	for emacs-orgmode@gnu.org; Thu, 14 Dec 2017 05:59:43 -0500
Received: from mout.kundenserver.de ([212.227.126.130]:49262)
	by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <rainer.stengele@online.de>)
	id 1ePREa-0000o8-NB
	for emacs-orgmode@gnu.org; Thu, 14 Dec 2017 05:59:25 -0500
In-Reply-To: <87fuc2ahmn.fsf@pinto.chemeng.ucl.ac.uk>
Content-Language: de-DE-1901
List-Id: "General discussions about Org-mode." <emacs-orgmode.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-orgmode/>
List-Post: <mailto:emacs-orgmode@gnu.org>
List-Help: <mailto:emacs-orgmode-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-orgmode>,
	<mailto:emacs-orgmode-request@gnu.org?subject=subscribe>
Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org
Sender: "Emacs-orgmode"
	<emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org>
To: Pdj <pauldj6@gmail.com>, emacs-orgmode@gnu.org

Am 04.09.2017 um 12:21 schrieb Eric S Fraga:
> On Monday,  4 Sep 2017 at 12:08, Pdj wrote:
>> Hello, I am observing this (funky?) behavior:
>> in the agenda, the deadline seems to be identified only if it
>> immediately follows the headline, and it is ignored otherwise.
>> Am I missing something?   Thank you, Paolo.
> 
> You are not missing something.  As the manual says:
> 
>      A timestamp may be preceded by special keywords to facilitate
>      planning.  Both the timestamp and the keyword have to be positioned
>      immediately after the task they refer to.
> 
> I guess immediately means not even a blank line.
> 
Hi,

it looks like

* TODO task
DEADLINE: <2017-12-14 Do>
SCHEDULED: <2017-12-14 Do>

will find the DEADLINE and SCHEDULE timestamp and display correctly in the agenda while

* TODO task
SCHEDULED: <2017-12-14 Do>
DEADLINE: <2017-12-14 Do>

will still find the SCHEDULED tinestamp but no more the DEADLINE.
I had this sequence in my org templates in the past and had no issues as far as I remember.
Has this behaviour changed?

Freshly creating a new SCHEDULED and DEADLINED timestamp results in the structure below.
Do all tasks now need to have both items in the same line like here:

* TODO task
SCHEDULED: <2017-12-14 Do> DEADLINE: <2017-12-14 Do>

Thank you.
Regards, Rainer

Org mode version 9.1.4 (release_9.1.4-206-g4b80c6.dirty ..