It’s like vim or emacs (or even got :) ) in that it has a logarithmic learning curve: steep up front, but the concepts you learn up front have a lot of leverage later on.
It’s like vim or emacs (or even got :) ) in that it has a logarithmic learning curve: steep up front, but the concepts you learn up front have a lot of leverage later on.
In the past I've tried to get to grips with emacs org-mode for the same thing, but Emacs.
And Ed Ream is super-responsive if there are issues
I'm making small changes to it, and actually have my own fork on GitHub with a change that I needed. But the developer doesn't seem to tend to it much.
I'll take a look at it. Tim Pope also has an independent plugin also called vim-markdown, I don't remember what the differences were between your upstream and his.
I'm not clear on what this term means. Can you explain how Leo helps with it, and what it means?
For example, you can link one part to appear on multiple locations of the document. Or you can write a script which filters the parts and rearranges them in your desired structure.
The point of something like leo editor is to have theoretically a unified way to do all that.