rofi-org-todo VS orgdown

(note and disclosure: I use a rofi compatible wayland package... and have actually written a rofi plugin to keep me in flow https://github.com/wakatara/rofi-org-todo )

I leave the todos in the daily files (in org super-agenda it gives them context) and then generally have org-roam links if they are related to a project and the person and then use tags like :perso: or :work: and usually a week if they are not scheduled (eg. :w49:), so they are separable in the agenda. This helps me focus on things that are important (also, you can tab to collapse or expand section using origami in super-agenda which helps to focus or not. I do have an inbox.org file for capture (and one called inbox13.org for my mobile device separately since I've had conflicts on Dropbox and iCloud before) though this is more to get stuff out of my head quickly (I'm the author of rofi-org-todo https://github.com/wakatara/rofi-org-todo ) and then I just process the inbox a la Dave Allen and usually put them with context notes in the daily file.

I use an Alfred (I'm on OSX) TODO capture which throws things into an inbox since I find that more comfy than in-emacs capture. If you are in Linux and use the (amazing) rofi, I also wrote a rofi mode to do the same thing for i3 and sway. Ubiquitous capture is definitely the way to go (and please read David Allen's Getting Things Done for more on that... =] ).

Unfortunately, "Org-mode" (or Orgmode) means two different things: (1) the lightweight markup syntax and (2) the Elisp implementation of a PIM/PKM tool within GNU Emacs.

This seems to be subtle but it results in many misunderstandings and unnecessary discussion issues.

To "solve" this situation, I tried to coin the term "Orgdown" for the syntax alone: https://gitlab.com/publicvoit/orgdown/ and https://karl-voit.at/2021/11/27/orgdown/

There are many use-cases to use Orgdown outside of Emacs and there are many tools that support Orgdown already: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Tool...

Although I'm using Orgdown and Org-mode for over a decade, I do think that even with an objective point of view, Orgdown does have its benefits from a syntax definition point of view in comparison to Markdown and other lightweight markup languages (LML): https://karl-voit.at/2017/09/23/orgmode-as-markup-only/

Oh and btw, the linked cheat-sheet covers only the most basic Orgdown syntax elements. Within the Orgdown concept, I defined misc "levels" of syntax elements, starting with OD1: https://gitlab.com/publicvoit/orgdown/-/blob/master/doc/Orgd... This also serves as some sort of cheat sheet I guess.

HTH

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.