A brief comparison of Leo and org mode. Org mode has these strengths:
- Drawers: visible, pure text, easily extensible uA's. - Agendas and tables. - In-pane rendering of Latex and special symbols. - Support for multiple source languages, including shell scripts, C, etc. - Code blocks, with arguments. - Result blocks. Leo will have all of the above this year. Leo has its own strengths: - Automatic tangling when saving files. - @others, missing from org mode's noweb markup. - Untangling: automatic update of @file nodes. Completely missing from org mode. In essence, all org mode files are @nosent files. - Importers. There are importers, but apparently none for programming languages. - Clones and especially clone-find commands. - API: org mode does have a hacking api <http://orgmode.org/manual/Hacking.html#Hacking>. It's oriented towards parsing body text. - DOM: org mode simulates a DOM with filters. Org mode data is fundamentally text. - Python scripting, including a python plugin architecture. There may be more ;-) *Conclusion*: It may still be true, in some limited areas, that Leo can do things that can even be *thought *in org mode. However, that statement is no longer generally true, and I'll remove it from all future documentation. All additions and corrections welcome. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
