Live data from Hacker News

Hello Worg, the Org-Mode Community

orgmode.org

21–30 of 53 posts

Re: Hello Worg, the Org-Mode Community

#21
post #13
post #9

So many good words, but they all miss the crucial point: you can't write a parser for org-mode. So elisp interpreted is needed to run the lisp code that defines it. It means that org-mode can be good while you are using it from emacs, and it sucks for anything else. I use markdown now, because you have a lot of tools to deal with markdown, while all tools for org-mode are bound to emacs. Which is perfectly fits the e…

Why can't a parser be written? Is there a halting problem or a grammar conflict? Or is "can't" short-hand for "too much trouble"?

> Why can't a parser be written?

Because the existing parser is written in truly emacs style: no formal grammar, just a lisp code with a regexp at each turn. Theoretically speaking it doesn't forbid you from writing a parser, but in practice there are no full-blown parsers of org-mode except the reference one.

Re: Hello Worg, the Org-Mode Community

#22
post #18
post #9

So many good words, but they all miss the crucial point: you can't write a parser for org-mode. So elisp interpreted is needed to run the lisp code that defines it. It means that org-mode can be good while you are using it from emacs, and it sucks for anything else. I use markdown now, because you have a lot of tools to deal with markdown, while all tools for org-mode are bound to emacs. Which is perfectly fits the e…

This is incorrect. You can write a parser for org. See for example https://github.com/tgbugs/laundry . Work toward standardization has been stalled because I (among others) have not had time to circle back to work on it. In part this is because the lack of a standard has not blocked most use cases since emacs is open source and can run almost anywhere.

> You can write a parser for org. See for example https://github.com/tgbugs/laundry.

Oh, there are a lot of incomplete parsers. This one is not an exception:

> Status

> Laundry can parse most of Org syntax, though there are still issues with the correctness of the parse in a number of cases.

> In particular there are a number of edge cases in the interaction between the syntax for various Org objects that have not been resolved.

I have my own parser as a pest grammar. It has just the basic features. This Laundry seems to implement more of org-mode, but I don't care anymore really, because I believe that org-mode will not be reimplemented.

> In part this is because the lack of a standard has not blocked most use cases since emacs is open source and can run almost anywhere.

I have some inexplicable aversion to an idea starting elisp interpreter just because my program needs org-mode parser. But even if I could integrate elisp into my program as easy as I do with lua, I probably wouldn't do it, because parser in lisp doesn't really solves the problem, it simplifies it a bit (I don't need to deal with the grammar) but shifts to another level: I need to learn how org-mode is represented as a lisp object. I need to reverse engineer the formal definition of that recursive object to deal with it, or turn on defensive programming expecting anything.

The only realistic way of dealing with org mode is to write code for emacs. There are exceptions of this rule, like pandoc, but I don't trust them.

Re: Hello Worg, the Org-Mode Community

#23
post #18
post #9

So many good words, but they all miss the crucial point: you can't write a parser for org-mode. So elisp interpreted is needed to run the lisp code that defines it. It means that org-mode can be good while you are using it from emacs, and it sucks for anything else. I use markdown now, because you have a lot of tools to deal with markdown, while all tools for org-mode are bound to emacs. Which is perfectly fits the e…

This is incorrect. You can write a parser for org. See for example https://github.com/tgbugs/laundry . Work toward standardization has been stalled because I (among others) have not had time to circle back to work on it. In part this is because the lack of a standard has not blocked most use cases since emacs is open source and can run almost anywhere.

> Work toward standardization has been stalled because I (among others) have not had time to circle back to work on it.

I tried to not to react to this, but, I'm sorry, I'm too much of a troll to just leave it without commenting.

Of course you have no time to write a formal definition. No one has time for that, and no one will have time for this. Because at this stage it is practically impossible. The parser was written as a bunch of regexps intermixed with lisp code. All edge cases were baked into org-mode because those regexps are the definition of org-mode. To write a formal grammar you need to catch all those edge cases, and to reproduce the behavior of the existing parser.

In retrospect, the parser should've been replaced with a formal grammar definition at much earlier stage, when it was possible to replace parser with another one, which is similar but generally incompatible because it deals with edge cases in a different ways. When the time was missed those edge-cases became a legacy you cannot fix.

Re: Hello Worg, the Org-Mode Community

#24

I hope org-mode gets more popular outside of Emacs. I know all the words already about how org-mode is great because of Emacs, but the way you can do plaintext outlining, with great support for TODO's, in org-mode is fantastic. It retains a lot of readability, and that isn't Emacs specific: there are things that make org-mode great as-is! A small todo application for mobile that uses org-mode as the database doesn't…

I sort of bounce off of org over and over because I find it very unreadable. Compared to Markdown (I know Markdown isn't quite the same thing), org feels very crusty and noisy.

Re: Hello Worg, the Org-Mode Community

#25
I was looking into org-mode after yet another system-collapse trying to manage everything in kanban (trello) + docs.

While it seemed like exactly what I needed, I was turned off by the TUI. So I kept looking and found something that, instead of running in a terminal, was effectively a Chrome browser, enabling all the "luxuries" of modern web apps while living on my local system.

Org-moders were definitely the OGs, but it's 2026 and the TUI novelty nostalgia, recently in full swing thanks to Claude Code, will wear off.

Re: Hello Worg, the Org-Mode Community

#26
post #11
post #9

So many good words, but they all miss the crucial point: you can't write a parser for org-mode. So elisp interpreted is needed to run the lisp code that defines it. It means that org-mode can be good while you are using it from emacs, and it sucks for anything else. I use markdown now, because you have a lot of tools to deal with markdown, while all tools for org-mode are bound to emacs. Which is perfectly fits the e…

There are incomplete parsers that cover most of the Org basics. For example, GitHub has one, crafted in Ruby. They use it to render e.g. readme.org files in repositories. It works quite well. I find the Org format very pleasant to work with. I think the trick with Emacs and Org is to stick to the basics and then only add features or change your configuration very slowly, as needed. I have been using Emacs non-stop fo…

> I have been using Emacs non-stop for >20 years and my .emacs is just 20 LOC. It's been shrinking, not growing.

Me too. I mean I'm using Emacs too, and it is 20+ years. I hate it deeply, and I cannot stop hating it because I cannot get away from it. I regret deeply choosing emacs 20+ years ago and spending 20 years to wrap my habits around it.

BTW my .emacs is still growing. I don't know how you manage to have 20 LoC of .emacs, I have a directory .emacs.d and a couple of dozen of files there. They are not large, some of them can be as small as 1 line. The last one I've wrote was dealing with indent of lua code. lua-ts-mode have some relatively simple rules that mostly work, but I was not happy with the result, there are some quirks that just are very inconvenient, and in some cases lua-ts-mode just fail to indent properly. So I fixed them to my taste. This one file is longer than 20 LoC.

Though, I should note, that LLMs make this much simpler. It is very simple to reverse-engineer what there is, and if you can explain the idea how to change the code, LLM can write all the elisp needed. It doesn't work out of the box, of course, and needs to be debugged, still LLM can save an hour or two.

> My goal is to bring it down towards 0 LOC.

You cannot. If you use lua you just cannot, because lua-mode uses indent of 3 spaces. Not 2, not 4, but three. So any lua sources you can find on github and try to edit will not be indented like lua-mode does. I cannot imagine what was going on the mind of the person who had chosen this value. The only possible explanation I have is something like "I want to be not like the others", but it doesn't seem right.

So you need at least to change lua-indent-offset (or lua-ts-indent-offset if you use treesitter), and it will be more than 0 LoC.

Re: Hello Worg, the Org-Mode Community

#27

I was looking into org-mode after yet another system-collapse trying to manage everything in kanban (trello) + docs. While it seemed like exactly what I needed, I was turned off by the TUI. So I kept looking and found something that, instead of running in a terminal, was effectively a Chrome browser, enabling all the "luxuries" of modern web apps while living on my local system. Org-moders were definitely the OGs, bu…

TUIs are great for when you know your tools well. But yeah, it’s 2026 and we’ve never been less aware of the nuance in the tools we use.

Re: Hello Worg, the Org-Mode Community

#28

I was looking into org-mode after yet another system-collapse trying to manage everything in kanban (trello) + docs. While it seemed like exactly what I needed, I was turned off by the TUI. So I kept looking and found something that, instead of running in a terminal, was effectively a Chrome browser, enabling all the "luxuries" of modern web apps while living on my local system. Org-moders were definitely the OGs, bu…

Terminal Emacs exists only so that experienced Emacs users can still get some approximation of their preferred setup when they're stuck unable to run the proper GUI version. I wouldn't pay too much attention to it.

Re: Hello Worg, the Org-Mode Community

#29
post #26
post #11

Earlier quoted context omitted.

There are incomplete parsers that cover most of the Org basics. For example, GitHub has one, crafted in Ruby. They use it to render e.g. readme.org files in repositories. It works quite well. I find the Org format very pleasant to work with. I think the trick with Emacs and Org is to stick to the basics and then only add features or change your configuration very slowly, as needed. I have been using Emacs non-stop fo…

> I have been using Emacs non-stop for >20 years and my .emacs is just 20 LOC. It's been shrinking, not growing. Me too. I mean I'm using Emacs too, and it is 20+ years. I hate it deeply, and I cannot stop hating it because I cannot get away from it. I regret deeply choosing emacs 20+ years ago and spending 20 years to wrap my habits around it. BTW my .emacs is still growing. I don't know how you manage to have 20 Lo…

:)

You could customize that variable instead, so that Emacs manages everything for you and you don't have to care that it would look like a line of code if you opened your settings and edited them directly.

Re: Hello Worg, the Org-Mode Community

#30

I hope org-mode gets more popular outside of Emacs. I know all the words already about how org-mode is great because of Emacs, but the way you can do plaintext outlining, with great support for TODO's, in org-mode is fantastic. It retains a lot of readability, and that isn't Emacs specific: there are things that make org-mode great as-is! A small todo application for mobile that uses org-mode as the database doesn't…

I sort of bounce off of org over and over because I find it very unreadable. Compared to Markdown (I know Markdown isn't quite the same thing), org feels very crusty and noisy.

This totally depends on how you set up your org face attributes. I keep using Org because, for me, it's far more readable than Markdown.

Also, it's always a tree. The three operations, like folding, traversal,. etc, are essential for me, and not available in Markdown.

Fortunately, GitHub understands README.org files.

Post reply on HN