From: David Talmage <david.talmage@shoutpoint.com>
To: Nick Dokos <ndokos@gmail.com>, emacs-orgmode@gnu.org
Subject: Re: Bug: org-mode interprets * as a headline in text between #+BEGIN_.. and #+END_...
Date: Fri, 7 Oct 2016 09:55:36 -0400 [thread overview]
Message-ID: <CAM6q_N7S8qhoSfrSgVMKqxn4N3HmsMe-Pk8dByzb0f0_EuRO2Q@mail.gmail.com> (raw)
In-Reply-To: <87y420lmgr.fsf@nicolasgoaziou.fr>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
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 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?
[-- Attachment #2: Type: text/html, Size: 1679 bytes --]
next prev parent reply other threads:[~2016-10-07 13:55 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 [this message]
2016-10-07 22:20 ` Nicolas Goaziou
2016-10-07 15:36 ` Nick Dokos
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAM6q_N7S8qhoSfrSgVMKqxn4N3HmsMe-Pk8dByzb0f0_EuRO2Q@mail.gmail.com \
--to=david.talmage@shoutpoint.com \
--cc=emacs-orgmode@gnu.org \
--cc=ndokos@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).