"Escaped" text fails to parse and reports an error about tree-sitter-org HOT 5 CLOSED

I need to introduce a conflict for matching \, (latex fragments, I believe). This should be an easy fix, but it falls into the markdown parsing that I want to export to queries + a possible tree-sitter-org-markdown parser that we'd discussed. I have time set aside next week to do some heavy lifting on all that.

from tree-sitter-org.

Awesome, thanks.
I'm not sure if it's possible, but it would be great to have parsing a bit more "loose". For example, an Emacs orgmode user tested some of his blog posts and got some parsing errors from random text in paragraphs. I'm not sure if this can be solved. Here's the link nvim-orgmode/orgmode#159

from tree-sitter-org.

Yeah this is exactly the kind of stuff I want to clean up, thank you for the reference. Removing the in-paragraph parsing (or exporting to a secondary parser) should solve a lot of this.

from tree-sitter-org.

I don't know if this is of any help, but I've recently (a few days ago) started writing an Org parser for Julia. It's a work in progress, but seems to be working so far using a hybrid recursive decent / linear parsing model. A few caveats do apply, for instance, I have no prior experience with writing parsers, and it's using a bunch of regex.

from tree-sitter-org.

This issue will be handled by queries in the next big update (see #13 and/or the markup-redo branch).

from tree-sitter-org.