From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Talmage Subject: Re: Bug: org-mode interprets * as a headline in text between #+BEGIN_.. and #+END_... Date: Fri, 7 Oct 2016 09:55:36 -0400 Message-ID: References: <874m4prv4x.fsf@gmail.com> <87y420lmgr.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=089e010d7fb8cdfa06053e46c38d Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39975) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsVcj-0001A3-1G for emacs-orgmode@gnu.org; Fri, 07 Oct 2016 09:55:42 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bsVch-0002sk-PB for emacs-orgmode@gnu.org; Fri, 07 Oct 2016 09:55:41 -0400 Received: from mail-wm0-x236.google.com ([2a00:1450:400c:c09::236]:35971) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bsVch-0002sJ-Br for emacs-orgmode@gnu.org; Fri, 07 Oct 2016 09:55:39 -0400 Received: by mail-wm0-x236.google.com with SMTP id k125so34131351wma.1 for ; Fri, 07 Oct 2016 06:55:38 -0700 (PDT) In-Reply-To: <87y420lmgr.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: Nick Dokos , emacs-orgmode@gnu.org --089e010d7fb8cdfa06053e46c38d Content-Type: text/plain; charset=UTF-8 On Fri, Oct 7, 2016 at 2:09 AM, Nicolas Goaziou wrote: > Hello, > > Nick Dokos writes: > > > Is the "* on column 0 is a headline" convention a consequence of the > > dependence on outline.el? Or is it just historical baggage? I cannot > > remember the grammar rules, but I'm wondering if the parser could be > > made to say "not a headline" in this situation, and if so, what the > > consequences might be (particularly, the bad consequences). > > ... > > This is inherent on how the syntax is defined, and how the parser is > implemented. As an outliner, the main syntactic element in an Org > document is the headline. Everything else has a lower priority. > Therefore, a block will not be parsed before a headline. > > ... That's interesting. Thanks for the explanation. What does the parser do with a drawer? How is that different from a block? It seems that one can put text that looks like a headline in a drawer and it won't be interpreted as a headline. Why couldn't blocks be parsed the same way? --089e010d7fb8cdfa06053e46c38d Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

= On Fri, Oct 7, 2016 at 2:09 AM, Nicolas Goaziou <mail@nicolasgoaziou.= fr> wrote:
Hello,

Nick Dokos <ndokos@gmail.com>= writes:

> Is the "* on column 0 is a headline" convention a consequenc= e of the
> dependence on outline.el? Or is it just historical baggage? I cannot > remember the grammar rules, but I'm wondering if the parser could = be
> made to say "not a headline" in this situation, and if so, w= hat the
> consequences might be (particularly, the bad consequences).
> ...

This is inherent on how the syntax is defined, and how the parser is=
implemented. As an outliner, the main syntactic element in an Org
document is the headline. Everything else has a lower priority.
Therefore, a block will not be parsed before a headline.

...

That&= #39;s interesting.=C2=A0 Thanks for the explanation.

What does the parser do with= a drawer?=C2=A0 How is that different from a block?=C2=A0 It seems that on= e can put text that looks like a headline in a drawer and it won't be i= nterpreted as a headline.=C2=A0 Why couldn't blocks be parsed the same = way?
--089e010d7fb8cdfa06053e46c38d--