From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: [new exporter] 2 questions
Date: Sat, 23 Feb 2013 13:36:27 +0100 [thread overview]
Message-ID: <874nh3jjg4.fsf@gmail.com> (raw)
In-Reply-To: <87obfbw7kj.fsf@Rainer.invalid> (Achim Gratz's message of "Sat, 23 Feb 2013 13:14:36 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Nicolas Goaziou writes:
>> IMO the parser already DTRT. In which case do you think it doesn't?
> DTRT is what you define as DTRT, so yes it does that already. At the
> very least it would be nice if the parser warned when it finds stray
> syntax pieces that are missing their match (it took me quite a while
> to see what was going on). If I look at the buffer I see things
> differently than the parser,
The parser parses Org syntax. If you see something else, unless there is
an obvious bug, then you are expecting the Org syntax to be different
from what it is. It's even the goal of the parser: to define the way to
read Org syntax.
Actually it is very simple to understand: elements have precedence over
objects. So in the following case:
--8<---------------cut here---------------start------------->8---
xxxx xxxx x x xxxxxxxxxxxx xxxxx xxxx xxxxxxxxxxxxxxx xxxx xxxxxxxx xxxx
x xxxx xx xx xx xxxxxxxxx xxxx xxxx x xx x x xx
- item 1
- item 2
--8<---------------cut here---------------end--------------->8---
there's a paragraph followed by a plain list, no matter what is found
within the paragraph.
And it's still the case when we replace "x" with tricky contents like:
--8<---------------cut here---------------start------------->8---
Some paragraph, something that looks like a link start [[#eisetu][and
something that looks like a math snippet \(2 + 3
- item 1
- item 2
--8<---------------cut here---------------end--------------->8---
> so some way to ask what the parser thinks I'm looking at would be nice
> (maybe that exists already, I don't know).
Usually fontification is a good indicator. Unfortunately, Org
fontification doesn't rely on the parser at the moment, so there are
some discrepancies.
Also, you're thinking backwards here: the parser doesn't have to think
about what you're looking at, as it knows it. Alas it can't know what
you're thinking you're looking at.
Anyway you can use (org-element-context) to know where point currently
is.
> And in all these cases where something inside an object or an element
> looks like it might be another element or greater element, we do need
> a way of quoting, I'd say.
No element can be found within an object.
So far, I don't see a need for quoting. In your previous example, you
know (or should know) that "- " as the first non-white string in a line
defines an item. You keep wanting to see a mathematical operation,
probably because you're focused on the LaTeX snippet you're writing, but
you're wrong wrt Org syntax.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-02-23 12:36 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 18:06 [new exporter] 2 questions henry atting
2013-02-22 19:04 ` Nicolas Goaziou
2013-02-22 19:38 ` henry atting
2013-02-22 19:42 ` Nicolas Goaziou
2013-02-22 20:13 ` henry atting
2013-02-22 20:19 ` Nicolas Goaziou
2013-02-22 20:31 ` henry atting
2013-02-22 20:33 ` Nicolas Goaziou
2013-02-22 20:39 ` henry atting
2013-02-22 21:39 ` Achim Gratz
2013-02-23 8:21 ` Bastien
2013-02-23 10:52 ` Nicolas Goaziou
2013-02-23 12:14 ` Achim Gratz
2013-02-23 12:36 ` Nicolas Goaziou [this message]
2013-02-23 13:04 ` Achim Gratz
2013-02-23 13:35 ` Nicolas Goaziou
2013-02-23 15:21 ` Achim Gratz
2013-02-23 15:31 ` Nicolas Goaziou
2013-02-23 16:35 ` Achim Gratz
2013-02-23 17:39 ` Nicolas Goaziou
2013-02-23 18:40 ` Achim Gratz
2013-02-24 9:09 ` Nicolas Goaziou
2013-02-24 10:31 ` Achim Gratz
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=874nh3jjg4.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=Stromeko@nexgo.de \
--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 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).