2 ms·

Looks like another iteration of someones personal markup-flavor, aimed at task-managment for self-organization. Basically, a todo-list in text-form. But I don'

Looks like another iteration of someones personal markup-flavor, aimed at task-managment for self-organization. Basically, a todo-list in text-form. But I don't see anything worthful yet which makes this flavor preferable over org-mode or markdown. Seems to be also still very in progress. So give it some more years to grow I would say.

zelphirkalt 5y ago
Markdown and Org are not in the same league. However, the goal is to have something like Org in (Neo)Vim. It will take a while, if it ever happens to get to feature parity with Org though. Edit: I would welcome though, if Org was supported well in (Neo)Vim. Then there would be one less excuse not to use it.
- slightwinder 5y ago
  > Markdown and Org are not in the same league. I don't think so. Their focus and culture is different and so each has different tools available, but syntax-wise they are pretty much the same and you can overall build the same tools for both.
  - zelphirkalt 5y ago
    Org comes more like an interconnected ecosystem, while in Markdown, you will have to choose your tooling wisely and will still not be able to do all the things you can do in Org. A few examples: Export to many formats. Emacs ox-... packages. Hit C-c C-e there you go. In Markdown there is no integrated tool for that, there is only the rather excellent Pandoc, but Pandoc itself suggests its own Markdown dialect (! not what we are talking about here) for things like footnotes and quotes and such things, which are required for technical writing. Running code from Org files in Emacs is, thanks to the Emacs integration of Org, a simple thing to do, once you got an interpreter / compiler installed and configured appropriately. This in conjunction with noweb (oh, did I mention that one?) enables literate programming. Yet another case of needing a specialized markdown dialect. LaTeX in Org mode documents is possible and the format takes precautions to enable you to do anything you want using LaTeX in an Org file. In Markdown it depends again on your Markdown processing tool. Again Pandoc to the rescue, mostly. Things like the already mentioned footnotes and citations and quotes. Some of that stuff is not available in Markdown. You can merely patch something up using HTML or, if you use Pandoc, perhaps you can add LaTeX to your document. This becomes a necessity, rather than a choice like in Org, because Org supports these things. Document internal linking. In Markdown you can again only patch it to full capability by using HTML. In Org it is included in the format. Tables and spreadsheets. You need special markdown dialects for that, which have special processing tools, which can then do half the things you can do in Org using spreadsheets. You can probably somehow shoehorn all of that into some kind of markdown dialect or multiple ones and process it using multiple external tools. It is just not there in normal Markdown and you will have to build the whole chain yourself or use some obscure tool, that has already showhorned it all. So Org and Markdown are really 2 different kinds of beasts. For more details you could join the Emacs-org-mode mailing list, where people all the time come with tricky questions and use-cases they are using Org for. Quite an active mailing list.
    - slightwinder 5y ago
      You're missing a bit the point. Markdown is today a family of flavors and tools, not just the original format made 2 decades ago. Yes, not all flavors have the same syntax, not all tools have the same abilities. Markdown-family today is quite chaotic, but also moving and consolidating. It's constantly evolving and moving forward. And while org-mode in it's single-app-cage provides a better offer in it's specific focus of abilities, markdown is not worse in general and also beats org-mode in other aspects. And in the meanwhile we also have tools emerging which start to beat org-mode&emacs even in their own strong points. One crucial apsect here is that markdown never had the strong focus on task-managment that org-mode had. This changed in the last years.
      - zelphirkalt 5y ago
        Hmmm. You are not really bringing any examples and we have moved the goalpost to all markdown dialects in existence and call it "markdown family" now. I think you will have to be more specific there to convince me.

zelphirkalt 5y ago

Markdown and Org are not in the same league. However, the goal is to have something like Org in (Neo)Vim. It will take a while, if it ever happens to get to feature parity with Org though. Edit: I would welcome though, if Org was supported well in (Neo)Vim. Then there would be one less excuse not to use it.

slightwinder 5y ago
> Markdown and Org are not in the same league. I don't think so. Their focus and culture is different and so each has different tools available, but syntax-wise they are pretty much the same and you can overall build the same tools for both.
- zelphirkalt 5y ago
  Org comes more like an interconnected ecosystem, while in Markdown, you will have to choose your tooling wisely and will still not be able to do all the things you can do in Org. A few examples: Export to many formats. Emacs ox-... packages. Hit C-c C-e there you go. In Markdown there is no integrated tool for that, there is only the rather excellent Pandoc, but Pandoc itself suggests its own Markdown dialect (! not what we are talking about here) for things like footnotes and quotes and such things, which are required for technical writing. Running code from Org files in Emacs is, thanks to the Emacs integration of Org, a simple thing to do, once you got an interpreter / compiler installed and configured appropriately. This in conjunction with noweb (oh, did I mention that one?) enables literate programming. Yet another case of needing a specialized markdown dialect. LaTeX in Org mode documents is possible and the format takes precautions to enable you to do anything you want using LaTeX in an Org file. In Markdown it depends again on your Markdown processing tool. Again Pandoc to the rescue, mostly. Things like the already mentioned footnotes and citations and quotes. Some of that stuff is not available in Markdown. You can merely patch something up using HTML or, if you use Pandoc, perhaps you can add LaTeX to your document. This becomes a necessity, rather than a choice like in Org, because Org supports these things. Document internal linking. In Markdown you can again only patch it to full capability by using HTML. In Org it is included in the format. Tables and spreadsheets. You need special markdown dialects for that, which have special processing tools, which can then do half the things you can do in Org using spreadsheets. You can probably somehow shoehorn all of that into some kind of markdown dialect or multiple ones and process it using multiple external tools. It is just not there in normal Markdown and you will have to build the whole chain yourself or use some obscure tool, that has already showhorned it all. So Org and Markdown are really 2 different kinds of beasts. For more details you could join the Emacs-org-mode mailing list, where people all the time come with tricky questions and use-cases they are using Org for. Quite an active mailing list.
  - slightwinder 5y ago
    You're missing a bit the point. Markdown is today a family of flavors and tools, not just the original format made 2 decades ago. Yes, not all flavors have the same syntax, not all tools have the same abilities. Markdown-family today is quite chaotic, but also moving and consolidating. It's constantly evolving and moving forward. And while org-mode in it's single-app-cage provides a better offer in it's specific focus of abilities, markdown is not worse in general and also beats org-mode in other aspects. And in the meanwhile we also have tools emerging which start to beat org-mode&emacs even in their own strong points. One crucial apsect here is that markdown never had the strong focus on task-managment that org-mode had. This changed in the last years.
    - zelphirkalt 5y ago
      Hmmm. You are not really bringing any examples and we have moved the goalpost to all markdown dialects in existence and call it "markdown family" now. I think you will have to be more specific there to convince me.