From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alan Tyree Subject: Re: DEADLINE: position in entry Date: Fri, 11 Nov 2016 08:05:29 +1100 Message-ID: References: <84twbg7n11.fsf@gmail.com> <87wpgbgyod.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c08581ac94f3c0540f8bb49 Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:57163) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1c4wXO-0000qq-Jr for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 16:05:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1c4wXM-00086K-SG for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 16:05:34 -0500 Received: from mail-yw0-x22f.google.com ([2607:f8b0:4002:c05::22f]:33810) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1c4wXM-00085p-Nj for emacs-orgmode@gnu.org; Thu, 10 Nov 2016 16:05:32 -0500 Received: by mail-yw0-x22f.google.com with SMTP id t125so259361916ywc.1 for ; Thu, 10 Nov 2016 13:05:31 -0800 (PST) In-Reply-To: <87wpgbgyod.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 Tyree , Samuel Wales , emacs-orgmode --94eb2c08581ac94f3c0540f8bb49 Content-Type: text/plain; charset=UTF-8 On 11 November 2016 at 02:08, Nicolas Goaziou wrote: > Hello, > > Alan Tyree writes: > > > 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. > > This is wrong. Only the keyword is ignored, not the timestamp. This is > why DEADLINE and SCHEDULED location is unrelated to section 8.1. > Hi Nicolas, Will you please double check this? On my system, the entry does *not* show up in the agenda (C-c a a). If I remove the DEADLINE:, then it does show up. So, for the important purpose under discussion, the timestamp is ignored. Emacs version 24.4.1 on Debian Stable org-version: Org mode version 9.0 (9.0-elpaplus @ /home/alant/.emacs.d/elpa/org-plus-contrib-20161102/) > > > 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. > > I think "immediately following the headline" is unambiguous. No need to > specify "no space or other text is allowed". > > I modified section 8.3 accordingly. > > WDYT? > > Subject to the above, OK. Just so long as there is a good strong warning about it. Thanks, Alan Regards, > > -- > Nicolas Goaziou > -- Alan L Tyree http://austlii.edu.au/~alan Tel: 04 2748 6206 sip:typhoon@iptel.org --94eb2c08581ac94f3c0540f8bb49 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On 11 November 2016 at 02:08, Nicolas Goaziou <mail@nicolasgoazio= u.fr> wrote:
Hello,

Alan Tyree <alantyree@gmail.com> writes:

> 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 prope= rly
> positioned or it will be ignored: see 8.3 for details.

This is wrong. Only the keyword is ignored, not the timestamp. This = is
why DEADLINE and SCHEDULED location is unrelated to section 8.1.

Hi Nicolas,
Will you please double = check this? On my system, the entry does *not* show up in the agenda (C-c a= a). If I remove the DEADLINE:, then it does show up. So, for the important= purpose under discussion, the timestamp is ignored.

Emac= s version 24.4.1 on Debian Stable

org-version: Org mode v= ersion 9.0 (9.0-elpaplus @ /home/alant/.emacs.d/elpa/org-plus-contrib-20161= 102/)


=C2=A0

> A timestamp may be preceded by special keywords to facilitate planning= .
> WARNING: both the timestamp and the keyword are ignored if not positio= ned
> immediately following the headline. No space or other text is allowed.=

I think "immediately following the headline" is unambiguou= s. No need to
specify "no space or other text is allowed".

I modified section 8.3 accordingly.

WDYT?

Subject to the above, OK. Just so long as there is a = good strong warning about it.
=C2=A0
Thanks,
Alan

Regards,

--
Nicolas Goaziou



--
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
--94eb2c08581ac94f3c0540f8bb49--