From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Bug? SCHEDULED lines treated differently when text precedes them Date: Thu, 5 Sep 2019 16:02:49 +0200 Message-ID: References: <874l1q9a9x.fsf@neron> <877e6mew38.fsf@nicolasgoaziou.fr> <87zhjiamo2.fsf@neron> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="000000000000e03e8f0591cec704" Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:54379) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1i5sM5-00088z-9X for emacs-orgmode@gnu.org; Thu, 05 Sep 2019 10:03:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1i5sM3-0005fA-LT for emacs-orgmode@gnu.org; Thu, 05 Sep 2019 10:03:21 -0400 Received: from mail-ed1-f42.google.com ([209.85.208.42]:36061) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1i5sM3-0005Yw-7N for emacs-orgmode@gnu.org; Thu, 05 Sep 2019 10:03:19 -0400 Received: by mail-ed1-f42.google.com with SMTP id g24so2817013edu.3 for ; Thu, 05 Sep 2019 07:03:07 -0700 (PDT) In-Reply-To: <87zhjiamo2.fsf@neron> 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: Christoph Groth Cc: org-mode list , Nicolas Goaziou --000000000000e03e8f0591cec704 Content-Type: text/plain; charset="UTF-8" On Thu, Sep 5, 2019 at 3:38 PM Christoph Groth wrote: > Nicolas Goaziou wrote: > > > Planning information (SCHEDULED, DEADLINE and CLOSED keywords) must > > appear right after the headline, per Org syntax. This is specified at > > the first paragraph in (info "(org) Deadlines and Scheduling"). > > > > Elswhere, only the timestamp is meaningful to Org. > > Thanks for the quick clarification! I didn't see the relevant line in > the documentation since my Emacs from Debian shows only the info > documentation for the (outdated) Org that is bundled with Emacs [1]. > This is, in fact, one of the very few things that did change with the introduction of org-elements.el and the fore formal parsing of Org files. Originally, SCHEDULED and DEADLINE could be anywhere in the entry. But with the development of the parser, and (I think) in order to define everything well in particular also for the export backends, the planning information was confined to the first line. I don't think you need to be worried about more surprises, this was the most significant one IIRC. Carsten > > I understand now that Org does what it should. However, I find this > behavior quite dangerous. It caught me after more than 10 years of > using Org. If there's a list of long-term issues with Org somewhere, > this problem may deserve being added to it. > > Cheers > Christoph > > [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=725408 > > --000000000000e03e8f0591cec704 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


=
On Thu, Sep 5, 2019 at 3:38 PM Christ= oph Groth <christoph@grothes= que.org> wrote:
Nicolas Goaziou wrote:

> Planning information (SCHEDULED, DEADLINE and CLOSED keywords) must > appear right after the headline, per Org syntax. This is specified at<= br> > the first paragraph in (info "(org) Deadlines and Scheduling"= ;).
>
> Elswhere, only the timestamp is meaningful to Org.

Thanks for the quick clarification!=C2=A0 I didn't see the relevant lin= e in
the documentation since my Emacs from Debian shows only the info
documentation for the (outdated) Org that is bundled with Emacs [1].

This is, in fact, one of the very few things = that did change with the introduction of org-elements.el and the fore forma= l parsing of Org files.=C2=A0 Originally, SCHEDULED and DEADLINE could be a= nywhere in the entry.=C2=A0 But with the development of the parser, and (I = think) in order to define everything well in particular also for the export= backends, the planning information was confined to the first line.

I don't think you need to be worried about more surpr= ises, this was the most significant one IIRC.

Cars= ten
=C2=A0

I understand now that Org does what it should.=C2=A0 However, I find this behavior quite dangerous.=C2=A0 It caught me after more than 10 years of using Org.=C2=A0 If there's a list of long-term issues with Org somewhe= re,
this problem may deserve being added to it.

Cheers
Christoph

[1] https://bugs.debian.org/cgi-bin/bugrep= ort.cgi?bug=3D725408

--000000000000e03e8f0591cec704--