From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: org-mode interprets * as a headline in text between #+BEGIN_.. and #+END_...
Date: Fri, 07 Oct 2016 11:36:37 -0400 [thread overview]
Message-ID: <87wphkqigq.fsf@gmail.com> (raw)
In-Reply-To: 87y420lmgr.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Nick Dokos <ndokos@gmail.com> 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).
>>
>> I'm not sure whether Nicolas has actually explained this situation in
>> the past, but, with gmane non compos mentis, I did not attempt to find
>> an earlier discussion.
>
> 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.
>
> The good side of headlines being top level elements is that parsing
> (without cache) only needs to start from the closest headline above. If
> blocks could be parsed before headlines, parsing should start from the
> beginning of the document every time.
>
Thank you. I appreciate both your patience and your explanations.
--
Nick
prev parent reply other threads:[~2016-10-07 15:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-06 20:28 Bug: org-mode interprets * as a headline in text between #+BEGIN_.. and #+END_ David Talmage
2016-10-06 21:13 ` John Hendy
2016-10-06 22:05 ` Nick Dokos
2016-10-07 6:09 ` Nicolas Goaziou
2016-10-07 13:55 ` David Talmage
2016-10-07 22:20 ` Nicolas Goaziou
2016-10-07 15:36 ` Nick Dokos [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wphkqigq.fsf@gmail.com \
--to=ndokos@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.