From mboxrd@z Thu Jan 1 00:00:00 1970 From: Rainer Stengele Subject: Re: DEADLINE ignored? Date: Thu, 14 Dec 2017 16:28:45 +0100 Message-ID: References: <87fuc2ahmn.fsf@pinto.chemeng.ucl.ac.uk> <813df7d1-1275-97c8-6f72-200b99f99b1b@online.de> <87fu8dv349.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:50838) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ePVRO-0006lM-St for emacs-orgmode@gnu.org; Thu, 14 Dec 2017 10:29:00 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ePVRK-0000RR-P8 for emacs-orgmode@gnu.org; Thu, 14 Dec 2017 10:28:54 -0500 Received: from mout.kundenserver.de ([212.227.126.135]:54876) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1ePVRK-0000PJ-FF for emacs-orgmode@gnu.org; Thu, 14 Dec 2017 10:28:50 -0500 In-Reply-To: <87fu8dv349.fsf@nicolasgoaziou.fr> Content-Language: de-DE-1901 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" To: Nicolas Goaziou Cc: Pdj , emacs-orgmode@gnu.org Am 14.12.2017 um 14:41 schrieb Nicolas Goaziou: > Hello, > > Rainer Stengele writes: > >> 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 > > Sheer luck, I would say. > >> * 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? > > I cannot remember Org supporting this syntax, actually. I don't think > anything 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> > > They do, but it's not new. > > Regards, > Thanks, Nicolas. I am concerned hearing you say "sheer luck" because I am relying on such double entries, which seem to have worked well in the past: * TODO [#A] Change tyres spring/autumn DEADLINE: <2018-05-01 Di> SCHEDULED: <2018-04-21 Sa +1y> DEADLINE: <2018-11-10 Sa> SCHEDULED: <2018-11-03 Sa +1y> So is that working only by sheer luck? Thank you. Regards, Rainer