#orgdown — Public Fediverse posts
Live and recent posts from across the Fediverse tagged #orgdown, aggregated by home.social.
-
@chiply @petrillic Unfortunately, the syntax #logseq is producing in Org-mode setting is far from being the same as how #Emacs is creating syntax elements: https://karl-voit.at/2024/01/28/logseq-from-org-pov/
Reading logseq files in Org-mode is probably fine. Modifying Org-mode generated/modified content in logseq most probably has some issues.
I've set up #logseq for my wife, now as logseq is going south (adding DB, losing org support, unclear future of file (sync) access,...) and I do have a medium-sized conversion problem with her data. 😞
It's better to start with #Orgmode right away: https://karl-voit.at/2020/01/20/start-using-orgmode/
-
Hi there, I wrote a mini PoC to illustrate what I'm looking for to edit #HTML files as #markdown or #orgdown text.
I'm challenging every #developer to try to do better with your own stack!
-
My article about "#Markdown Is a Disaster: Why and What to Do Instead" from https://karl-voit.at/2025/08/17/Markdown-disaster/ was listed on the entry page of #HackerNews yesterday.
It hurts me to read through the comments. One part of the people who commented obviously didn't read the article they're commenting on.
And another part of the commenters does mix up #Orgmode, the Elisp implementation within #Emacs, with orgdown, the lightweight syntax which is actually the topic of this article. This part of the discussion is totally missing the whole point of my article: practical issues related to Markdown; choosing any other #LML which doesn't come with those downsides. #Orgdown was just one example of many which I wanted to mention because it is one of the least known alternatives outside the Emacs bubble.
🤷
-
@ericsfraga @oantolin Yes, the direct and initial benefits of #Orgdown are mostly for non-Emacs people: https://karl-voit.at/2021/11/27/orgdown/
However, just imagine for a minute, that all #Markdown usage is replaced with Orgdown usage. Let your thoughts wander for a moment.
This would have tremendous impact on the #Emacs people as well when it comes to working with external tools and people.
#PIM #LML #indirectprofitability #markup #publicvoit #orgmode
-
Besides not using a better #LML syntax such as #Orgdown, I really do like the way how @silverbulletmd is transparent about its #Markdown downsides.
That's why I extended my article on the downsides of Markdown with it as an example: https://karl-voit.at/2025/08/17/Markdown-disaster/
-
Any recommendations for an Android app to read (only) and search through ten mid-size to large #orgdown files I currently sync via Syncthing?
#Orgzly revived does kill captured data (in my setup situation) and #Orgro can't even open my larger files.
Edit: logseq Android is not good with large files + search results. Unfortunately, this doesn't work either.
Edit: Emacs without physical keyboard and being on the go is not an option to me.
-
@yojimbo @screwlisp Maybe.
In best case, this would be a discussion within the org community and not my personal decision any more.
So far, nobody expressed interest in contributing to the idea/concept but I'm more than happy if this would change and I'm out of the game in terms of a one person project.
The community could then define a new name, next steps, OD2, ...
-
In a couple of hours (8am UTC, 10am CET), I'll be live on the #screwtape channel by @screwlisp on https://communitymedia.video/c/screwtape_channel/videos
We'll be talking about #Markdown and #Orgdown because I recently published "Markdown Is a Disaster: Why and What to Do Instead" https://karl-voit.at/2025/08/17/Markdown-disaster/
-
#Markdown Is a Disaster: Why and What to Do Instead
https://karl-voit.at/2025/08/17/Markdown-disaster/Here's my article where I summarize the subtle and no so subtle downsides when you choose Markdown for your information instead of a different markup syntax that doesn't come with all the downsides of #MD.
#publicvoit #orgdown #orgmode #LML #pandoc #rst #restructuredtext #asciidoc #Wikitext #BBCode #Creole #Crossmark #Djot #CommonMark #lockin
-
Yes, it is: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
However, I'll publish at least 2 articles over the next weeks that summarize the issues and #lockin effects of #Markdown.
The solution is not just #orgdown but any lightweight markup language (#LML) that lacks the downsides of Markdown: heavy fragmentation, too many issues when processed via tools, inconsistent design, hard to learn and type, ...
Orgdown is just one of many candidates. 🙇
(IMO the best but that's open to subjective opinion.)
-
Absolutely.
#orgdown = the name for the syntax of Org-mode which can be used anywhere and which got great support outside of Emacs just as #Markdown has support outside any MD tool you name including pandoc.
#orgmode = Elisp implementation to Support note-taking (and much more) with a #LML named orgdown in (GNU) Emacs with highlighting and modification features.
Background:
https://karl-voit.at/2021/11/27/orgdown/
https://gitlab.com/publicvoit/orgdown/And my current main article on that:
Org Mode Syntax Is One of the Most Reasonable Markup Languages to Use for Text
https://karl-voit.at/2017/09/23/orgmode-as-markup-only/I'll publish an article on the many downsides of Markdown in a few weeks. You might want to add my blog feed to your RSS aggregator.
-
@zstg @thelinuxcast We should actually get rid of #Markdown. 😉
It is one of the worst lightweight markup languages you can decide for except for adoption: it's bad with respect for learning, for typing manually and for processing.
Avoid the Markdown flavor hell and go for any other #LML that doesn't come with all the downsides.
#orgdown, the syntax of #orgmode is one of the examples where the downsides of Markdown are avoided.
Please, don't settle for a mediocre solution again.
-
@gnulinux Stay tuned. Ich habe zum Thema #Markdown + dessen fürchterliche (und zum Teil subtile) Nachteile eine Artikelserie in Arbeit.
Da dies oft zu Missverständnissen führt, musste ich da etwas ausholen - kostet viel Zeit zum Recherchieren & Schreiben.
Den Großteil habe ich bereits.
Nur soviel: statt MD sollte man Lightweight Markup Languages (#LML) verwenden, die in ihrer ursprünglichen Definition bereits so definiert wurden, dass man die wichtigsten Syntaxelemente nicht erst mit (zueinander inkompatiblen) Flavors usw. bekommt.
MD hat ja schon in der Urform beispielsweise zwei unterschiedliche Typen von Headings definiert. 🤦♂️
#Orgdown ist so ein Vertreter, das meiner Meinung nach auch die beste Wahl für einen Ersatz zu Markdown ist. Ein Umstieg hat - je nach Anforderungsset - durchaus viele Vorteile, die man erst dann erkennt, wenn man mal Markdown losgeworden ist. Und da zähle ich den hervorragenden Tool-Support durch #Emacs noch gar nicht dazu. Der ist auch optional. :emacs:
-
#LibreOffice möchte #Markdown unterstützen: https://www.heise.de/news/LibreOffice-erhaelt-Markdown-Support-10477309.html
Dumme Idee.
-
Should I dare to do a "why #Markdown is one of the worst lightweight markup syntax languages there is"-session at a UX/UI-dominant #barcamp? 😜
C'mon, do push me over that cliff! 😆
Background: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/ 👉 it's related but would be a different focus since I won't push #orgdown that much - people can be happier with other LMLs as well as long as it's not the #MD hell. (Sneak preview: I'm writing a long article on all the MD issues in order to explain it once and for all since the Mastodon discussions are really annoying to me.)
-
Of course, if you do have long-time plans for your personal #knowledgemanagement, you should not use proprietary tools like #Obsidian, #OneNote, #Evernote and alike.
You also should think of switching to a much better (learnability, portability/compatibility, typobility, logic, featureset) markup syntax like #orgdown which is used in #Emacs #Orgmode (among other tools).
But if you start with Org-mode, you need to know the right way of doing it, as so many web pages recommend. Here's my take:
#UOMF: The Right Way to Use #OrgMode
https://karl-voit.at/2021/08/30/the-org-mode-way/ad syntax/Markdown/Orgdown/#LML: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
A specific blog post about the #lockin effects of Obsidian and Co (despite using some tool-specific flavor of MD) is in the making. (Please don't start a religious discussion here.)
-
@ajlewis2 @ellane @feralthoughts @hbowie @reichenstein
Just for clarification: same holds true for any other markup supported by pandoc, not just #Markdown.
However, if you stick with a syntax language that doesn't come with this explosion of flavors, you have less issues converting your data - in some cases you don't even have to convert at all any more.
The issue with Markdown is that its original form defined a small minimum of elements and each tool defined its own potentially incompatible extensions. With other #LML, the "original" or its standard defines the maximum set of elements and therefore, there is no need for "flavors" and no data loss or conversion effort.
HTH
-
@amoroso My thoughts:
- They mix up Markdown with the general term lightweight #markup language (as if #Markdown is the only #LML syntax)
- They ignore all other markup syntax examples such as (La)TeX, HTML, ...
- great screenshots of Word for DOS upwards 👍
- the title should be "#WYSIWYG vs. LML" (instead of the Word vs. Markdown story)
- no mentioning of other LML examples
Well it looks, as if we're settling for a mediocre standard again.
Related: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
-
With #Markdown, the original (inconsistently designed) #LML syntax format is a minimal set that made much sense when used when typing emails and so forth. Later-on, various tools needed more syntax elements for obvious reasons. Those syntax add-ons extended the original Markdown. However, they were not standardized.
This resulted in a zoo of very similar but incompatible set of Markdown flavors. Those differences cause information loss by moving from one "Markdown" tool to another "Markdown" tool because Markdown is not Markdown in most cases.
In contrast to that, #orgdown, the syntax of #Emacs #orgmode, as the one and only original form has - by far - the largest set of syntax elements and various extensions by modules. Any other adaptation of this syntax in other tools chose a real sub-set of the original syntax elements. This makes data transitions much smoother, is less error-prone and causes less data loss.
More on that: https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
-
@pandoc Great idea!
Let's introduce one slightly change at a time and in a few years we could transform #Markdown into #orgdown without anybody noticing and finally get a consistently designed and easy to learn lightweight #markup language with excellent tool support. 😈
https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
https://gitlab.com/publicvoit/orgdown -
@ellane Oh, congrats to this new universe of opportunities. 😎
Coming from that direction, you might want to read:
https://karl-voit.at/2017/09/23/orgmode-as-markup-only
...still related to the syntax & following related to tooling:
https://karl-voit.at/orgmode/
https://karl-voit.at/2020/01/20/start-using-orgmode/Meanwhile, I'm writing in #Orgdown & generate any #Markdown from that because there's no MD tooling that is able to compete.
Btw, I'll publish an article on lock-in effects related to MD-based tools like #Obsidian.
-
#Orgdown (= #OrgMode Syntax) Is One of the Most Reasonable #Markup Languages to Use for Text https://karl-voit.at/2017/09/23/orgmode-as-markup-only/
#publicvoit #LML #markdown #AsciiDoc #Wikitext #reStructuredText #rst #pandoc