org-parser VS orgdown

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

Hi there, maintainer of organice here. Even before publicvoit started the great effort of orgdown, we've started working on a standardized Org mode parser which will run for different programming languages and runtimes: https://github.com/200ok-ch/org-parser

Having said so, since orgdown is a subset of Org mode, organice fully supports orgdown. Technically and as a project.

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

org-element-parse-buffer 'element granularity (7.688000744 0 0.0) 8sec tree-sitter via https://github.com/milisims/tree-sitter-org parsed down to 58% of the buffer in 5.3sec extrapolates to ~9sec Racket's brack via https://github.com/tgbugs/laundry failed to finish parsing in reasonable time. Cancelled at 10m11.436s Clojure parser via https://github.com/200ok-ch/org-parser failed to finish parsing with java.lang.OutOfMemoryError: GC overhead limit exceeded Running time 8m28.078s

The official specification of org-mode did a good job, but it is not machine readable nor formal. So there are only tests (but no proofs) for that the official parser (org-element.el) really does what the spec says. It would be nice if the official org-mode can have such a formal specification. (For other benefits, see this).

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

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...

There are two reasons why I call Org mode standardized.

> I imagine there aren't really various flavors of Org Mode, but that doesn't make it standardized.

All the implementations that call themselves org-mode follow the conventions set by the canonical implementation - the Emacs org-mode. While this may not sound like a good reason to call it standardized, the practical implication is a vast difference from what you get with various markdown flavors. In the latter case, the only way to make sure that your markdown is correct, is to test it with the target implementation.

The second reason is that there is an actual effort to standardize org-mode - called Orgdown [1]. Org-mode is already more or less uniform across implementations. This effort tries to write it down as a reference. Markdown has a similar effort called CommonMark. But if you want to know why it's different, you have to look at the history of why it isn't called 'Standard Markdown'.

[1] https://gitlab.com/publicvoit/orgdown

And yes, at least my setup fulfills all of your requirements and much more. For starters, I can add tags, date- and timestamps everywhere, generate "agenda" views for days/weeks/months/... which collects all those time-related items and visualizes them, I can link emails/urls/... and links to files which I tag as well, I can search through search strings or regex to find meta-data on files/notes/events/... and it's all in the most versatile file format possible: plain UTF-8 text files containing simple orgdown syntax, the most beautifully designed lightweight markup language (LML) there is IMHO.

Are you aware of orgdown?

If you want to parse Orgdown files yourself, expect to invest some time in setting up a testing environment.

I think we've got a misunderstanding here. Text files (in this case in orgdown syntax format) are files that contain the information in its original form: characters, words, sentences. So you only need a software that lets you open a text file to view it. If you want to modify the information stored in the text files, you need an application that lets you modify text files. In case of orgdown, you can find options on https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool-Support.org or choose any non-syntax-specific editor of your choice.

So the links are working in Markdown? So Markdown-export is working and your issue starts with the conversion from Markdown to Orgdown?

Well, the difference is that Orgdown, the syntax of Org mode for GNU Emacs is a Lightweight markup language while HTML is a more complex markup language.

Since your notes are in orgdown format, you may use any compatible app that understands to read and probably write orgdown. One of them is GNU Emacs with its org-mode.

I'm thinking of a screen that pops up when booting Emacs that only shows the files I was working on recently in large font (maybe as buttons to click on). The file extension should be hidden, so that I may use it with Orgdown files that have long, descriptive file names (most probably within the same directory).

Accessing your Org mode based knowledge management base outside of GNU Emacs: Orgdown has very good support for all sorts of platforms including mobile ones.