Jakob Schöttl

Even single-line styles have severe problems in EBNF. I want to check out, if it is reasonable to put all style (emphasis and verbatim, how it's called in the spec)...

Note to self: 1. Check if it's OK or "allowed" that emphasis spans other elements that are already parsed via EBNF. E.g. `*this [[url]] is bold and _O_2 is also...

Regarding 2.: instaparse has a built-in way to get position/location meta information from the parse tree! Even if the parse tree looks like it only holds the parsed data, the...

Good idea. I think it would already be usefull now, even if we don't yet support everything from organice. But at least, there should be no parse failures.

Hi and thanks for opening this discussion, the idea of a common base of test org files for parsers came already up a while ago somewhere... I don't remember. However,...

Alright, feel free to post here again and re-open the issue, I'm interested in news :) I also have little experience with PEG. It combines the EBNF with additional "logic"...

Wow, interesting, thanks for that link, @nightscape ! I hope I find some time to try that.

Another benchmark: @alexpdp7 wrote [instaparse-cli](https://github.com/alexpdp7/instaparse-cli) which compiles to a binary. I just did a benchmark: ``` $ wc -l ~/org/notes.org 1883 $ time ./instaparse-cli ~/projects/org-parser/resources/org.ebnf ~/org/notes.org > /dev/null real 0m4.173s...

How about this sample org file: ```Make sample.org: README.org ~/projects/organice/README.org ~/projects/organice/sample.org cat $^ > $@ ``` It's only ``` $ wc -l sample.org 1638 sample.org ``` lines. But it uses...

Hm, almost anything is `text`. Is that rule really costly or does it just take most of the processing time? ``` text = ( timestamp / link-format / footnote-link /...