org-parser VS org-ql

Let me start by saying I like the goal and would like to see org mode accessible to everyone, but I do have some thoughts/reservations.

> For the little code I do write, I find having AI assistance (via CoPilot or Cody) to be tremendously helpful. So helpful, in fact, that I now tend to jump into VSCode for actual coding,

Aren't there both copilot and Cody plugins available in emacs?

> Use VSCode for everything. For me, this requires a full-featured org mode implementation. I currently feel stuck in Emacs just because of how great org mode is.

This seems much more difficult than creating plugins you need in emacs and with the downside that customization will be much worse in vscode, especially customization of behavior with things like hooks.

> Letting go of bug-for-bug compatibility with Emacs as a goal. Let's let the quirky behavior die off and move forward with a more cohesive program, even if it looks a little bit different.

If you don't have compatibility, then you aren't really implementing org-mode... you are starting fresh.

That's okay, but you'll likely annoy org-mode users and developers as documents ending in `.org` start not working the same.

Also there are languages besides Rust and Haskell that have an org parser implementation. For instance one written in Javascript already has a spec as you explain it and is used in production for organice[0]:

> Why is this project useful / Rationale

> Org mode in Emacs is implemented in org-element.el (API documentation). The spec for the Org syntax is written in prose. - https://github.com/200ok-ch/org-parser

> Portable. It should not be difficult to get this integrated into any editor.

This tells me you already have a language in mind such as Lua (can't think of any other easy to integrate languages)? I'd argue that's not very popular either though.

0: https://organice.200ok.ch/

I mean , you have parsers for JS and CLJS https://github.com/200ok-ch/org-parser

I don't think you did. You probably used the sister project https://github.com/200ok-ch/org-parser which has a well known issue regarding what you are describing: https://github.com/200ok-ch/org-parser/issues/56

organice has no such performance issues (and does not run on the JVM). I use it daily with 5k LOC files.

EBNF grammar - https://github.com/200ok-ch/org-parser/blob/master/resources...

From the readme:

> Org grammar for tree-sitter. It is not meant to implement emacs' orgmode parser, but to implement a grammar that can usefully parse org files to be used in neovim and any library that uses tree-sitter parsers.

This grammar is in active development and is being used by nvim-orgmode/orgmode [1], a org-mode neovim plugin.

Some additional resources some might find useful:

* Org Syntax - https://orgmode.org/worg/dev/org-syntax.html

* EBNF grammar - https://github.com/200ok-ch/org-parser/blob/master/resources...

[1] https://github.com/nvim-orgmode/orgmode

There's at least a parser using that as a spec at https://github.com/200ok-ch/org-parser

We have an issue with more information and we are working on it: https://github.com/200ok-ch/org-parser/issues/56

If you’re open to use a different Lisp, then maybe https://github.com/200ok-ch/org-parser is something for you.

I just wanted to chime in and mention that the folks who wrote organice[0] also came up with an EBNF grammar[1] for org-mode. Also of tangential interest is that work is actively being done on creating a tree-sitter version[2] of the grammar, although that work is not public (yet).

[0] https://github.com/200ok-ch/organice

[1] https://github.com/200ok-ch/org-parser/blob/master/resources...

[2] https://github.com/kristijanhusak/orgmode.nvim/issues/31#iss...

Also Org-ql, maybe with some sort merging with org-agenda (Because writing configurations of org-agenda is a PITA, too.)

I don't know about pure org, but you could try org-ql. Check org-ql-find-in-org-directory.

See https://github.com/alphapapa/org-ql

I don't know about how it's done in vanilla org, even though I'm fairly sure it's possible. Still, this can be very easily done with the org-ql package: https://github.com/alphapapa/org-ql

alphapapa/org-ql.

See also this WIP branch of org-ql that provides org-ql-report views, which allow multiple queries to be displayed and grouped in a single buffer: https://github.com/alphapapa/org-ql/issues/331

I don't use it, but you may want to take a look at org-ql, specifically the org-ql-search command, which does something similar. It may or may not be what you want.

org-ql-find/org-ql-search (from org-ql) work nicely even with datetrees.