On Thu, Aug 1, 2019 at 8:03 PM Jeff R. <[email protected]> wrote:
Here are the reasons why I use emacs: [org mode and elisp]. > Thanks for this. It lead me to a big aha, which I'll describe in another post. 1. > > The benefit elisp is that, with just a bit of knowledge, I can write > custom functions on the fly, bind them to a shortcut, and be done. > That's what @command and @button do. They aren't statically bound, so you can change the contents of an @button node/tree and re-execute it with the new code. > The language itself provides simple functions for navigating the buffer, > navigating between buffers, text entry, changing color, etc. > Leo's api does all this, using the predefined c, g and p values. > Emacs also does an excellent job of exposing its documentation. > Leo's help-for commands are loosely based on the emacs equivalent. ipython/jupyter do better at this kind of thing. > Also if you want to see some quick videos of emacs-style tricks, checkout > the emacs rocks videos on youtube. > I am aware of this series. BTW, Leo used to have emacs-style macros. We retired them because nobody seemed to care. Of course, as soon as we did that, people started to complain. Regardless, if you could do orgmode--or something like it--in Leo I think > that would be a big selling point. It would for me, at least, since python > is just easier to use than elisp, no matter how cool it is. > Imo, Leo is org mode on steroids. The problem isn't with Leo's outlining, the problem is trying to keep up with the huge number of users continually improving emacs. Which lead to the Aha... 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/CAMF8tS3SNAjOFwyCOjdUwRshLto5UkskG8UOvBEJ%3DBhR0z7P7A%40mail.gmail.com.
