Leo already works fairly well with vim, emacs and ipython. However, I think Leo's file format could be friendlier to emacs's org-mode outlines.
I call this project "compatibility mode". As always, the big question is "what to do about clones?" org-mode uses sentinels similar to Leo's latest file format, but org-mode knows nothing of gnx's and clones. When writing, Leo would simply ignore gnx's. All nodes, clone or not, would get written in the org-mode format. As always, there are more choices when reading. One could choose that all nodes with the same headline and body text would become clones of each other. Or one could say that clones are never created. As I write this, I see that org mode could (optionally) put @gnx directives in the org-mode file, and use same to recreate clones. Of course, this would pollute the body of the org-mode file, but then one could say that any other Leo directives could be called form of pollution. Anyway, the details about clones aren't the main idea. It would be an important bridge to emacs if (optionally) Leo could write and read standard org-mode files. Similar remarks probably apply to vim-outline mode. Org mode won't be part of Leo 4.11, but it might be part of Leo 5.0. Your comments please. -- 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 http://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/groups/opt_out.
