From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Tyree Subject: Re: DEADLINE: position in entry Date: Thu, 10 Nov 2016 10:59:49 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c0970b86830500540e70db5 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:37592) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4cmW-00057k-O4 for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:59:54 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4cmV-0008Qa-OP for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:59:52 -0500 Received: from mail-yb0-x22c.google.com ([2607:f8b0:4002:c09::22c]:36303) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4cmV-0008QC-FW for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:59:51 -0500 Received: by mail-yb0-x22c.google.com with SMTP id v78so83580863ybe.3 for ; Wed, 09 Nov 2016 15:59:51 -0800 (PST) In-Reply-To: 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: Samuel Wales Cc: emacs-orgmode --94eb2c0970b86830500540e70db5 Content-Type: text/plain; charset=UTF-8 On 10 November 2016 at 10:47, Samuel Wales wrote: > iirc we've discussed whether planning lines (i.e. scheduled, deadline, > closed at this time) should be flexible. we concluded to make them > strict. > > check archives for the discussion. :) everything goes through this > mailing list. > > OK, I'll accept that and have a look at the rationale. However, since DEADLINE: is so terribly important, I think that there should be a prominent warning in the manual that they are simply ignored if not positioned correctly. Warnings should appear, at the very least, in 8.1 and 8.3. Suggested wording: In 8.1: timestamp can appear anywhere in the headline or body of an Org tree entr UNLESS is is preceded by a keyword in which case it must be properly positioned or it will be ignored: see 8.3 for details. In 8.3: A timestamp may be preceded by special keywords to facilitate planning. WARNING: both the timestamp and the keyword are ignored if not positioned immediately following the headline. No space or other text is allowed. Regards, Alan > -- > The Kafka Pandemic: http://thekafkapandemic.blogspot.com > > The disease DOES progress. MANY people have died from it. And > ANYBODY can get it. > > Denmark: free Karina Hansen NOW. > UPDATE 2016-10: home, but not fully free > -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c0970b86830500540e70db5 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 10 November 2016 at 10:47, Samuel Wales <samologist@gmail.com> wrote:
ii= rc we've discussed whether planning lines (i.e. scheduled, deadline, closed at this time) should be flexible.=C2=A0 we concluded to make them strict.

check archives for the discussion.=C2=A0 :) everything goes through this mailing list.

OK, I'll accept that and have a look at the rationale. Ho= wever, since DEADLINE: is so terribly important, I think that there should = be a prominent warning in the manual that they are simply ignored if not po= sitioned correctly. Warnings should appear, at the very least, in 8.1 and 8= .3.

Suggested wording:

In 8.1:

<= br>timestamp can appear anywhere in the headline or body of an Org tree
= entr UNLESS is is preceded by a keyword in which case it must be properly p= ositioned or it will be ignored: see 8.3 for details.



--
Alan L Tyree=C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://austlii.edu.au/~alan
Tel:= =C2=A0 04 2748 6206=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0= =C2=A0=C2=A0 s= ip:typhoon@iptel.org
--94eb2c0970b86830500540e70db5--