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:44:52 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> <87eg2ki5tz.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c07e550ea4c040540e6d732 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:34547) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4cY6-0000w6-Pn for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:45:02 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4cY1-0000yv-Iy for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:44:58 -0500 Received: from mail-yw0-x22c.google.com ([2607:f8b0:4002:c05::22c]:33118) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4cY1-0000yZ-ED for emacs-orgmode@gnu.org; Wed, 09 Nov 2016 18:44:53 -0500 Received: by mail-yw0-x22c.google.com with SMTP id r204so226394566ywb.0 for ; Wed, 09 Nov 2016 15:44:53 -0800 (PST) In-Reply-To: <87eg2ki5tz.fsf@nicolasgoaziou.fr> 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: Alan L Tyree , emacs-orgmode --94eb2c07e550ea4c040540e6d732 Content-Type: text/plain; charset=UTF-8 On 10 November 2016 at 10:36, Nicolas Goaziou wrote: > Hello, > > Alan L Tyree writes: > > > On 10/11/16 05:51, Philip Hudson wrote: > > > Also, if this really is the case, then the manual needs to be > > modified. Under 8.1, it says > > > > " A timestamp can appear anywhere in the headline or body of an Org tree > > entry." > > Section 8.1 is about regular time-stamps, which are not necessarily tied > to DEADLINE and SCHEDULED keyword. Therefore, the sentence above is > true. > > > and under 8.3: > > > > "A timestamp may be preceded by special keywords to facilitate planning:" > > > > I can't see anywhere that requires the DEADLINE: keyword to be flush > > against a heading. > > This is in 8.3.1, first footnote. > > So it is. Not exactly prominent :-). I still think the manual is misleading, and is there some reason that "planning" items are treated different from plain old appointment timestamps? I just seems (to a non-programmer) to be an unnecessary restriction. Cheers, Alan > Regards, > > -- > Nicolas Goaziou > -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c07e550ea4c040540e6d732 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 10 November 2016 at 10:36, Nicolas Goaziou <mail@nicolasgoazio= u.fr> wrote:
Hello,

Alan L Tyree <alantyree@gmail.com= > writes:

> On 10/11/16 05:51, Philip Hudson wrote:

> Also, if this really is the case, then the man= ual needs to be
> modified. Under 8.1, it says
>
> " A timestamp can appear anywhere in the headline or body of an O= rg tree
> entry."

Section 8.1 is about regular time-stamps, which are not necessarily = tied
to DEADLINE and SCHEDULED keyword. Therefore, the sentence above is
true.

> and under 8.3:
>
> "A timestamp may be preceded by special keywords to facilitate pl= anning:"
>
> I can't see anywhere that requires the DEADLINE: keyword to be flu= sh
> against a heading.

This is in 8.3.1, first footnote.

So it is. Not exactly prominent :-). I still think th= e manual is misleading, and is there some reason that "planning" = items are treated different from plain old appointment timestamps? I just s= eems (to a non-programmer) to be an unnecessary restriction.

<= div>Cheers,
Alan
=C2=A0
Regards,

--
Nicolas Goaziou



--
A= lan 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 sip:typhoon@iptel.org
--94eb2c07e550ea4c040540e6d732--