4 ms·
For me it's the editor tools. Keeping my projects/todos/etc in a text file that is organized outliner style is really good, the org specific editor commands mak
by freshhawk 9y ago
For me it's the editor tools. Keeping my projects/todos/etc in a text file that is organized outliner style is really good, the org specific editor commands makes changing that file easy.
Having the agenda view (calendar) generated, having sparse trees, having spreadsheet like tools, having precise and intuitive folding behaviour make it great.
I don't care at all about the whole org->html pipeline. Who cares. It's not very good and it isn't better than markdown. I get that if you are already in the org world it's nice, but it's not the reason to get into that world.
- frankzinger 9y ago> I don't care at all about the whole org->html pipeline. Who cares. It's not very good Sure, you probably wouldn't use it to generate a large, professional website, but I've found it (HTML generation) to be surprisingly customisable and definitely very useful in many cases where one might otherwise write HTML by hand or even in markdown. > and it isn't better than markdown. What can markdown do that org cannot? Also, org mode exports to markdown (among many other formats) and its strong support in emacs means the text-editing experience is probably going to be much better than it would be in markdown (in any editor, I would bet).
- freshhawk 9y agoI'm pretty fluent in org and I still just write it up in markdown or with a zen coding plugin or in hiccup. Although I do occasionally export my org stuff to html for one reason or another. It's really list focused obviously but I don't dislike it, it just doesn't solve any problems for me.