3 ms·
I've wanted to use this for a few years, and finally dived in this year. The good: If you can wrap your head around it and spend a fair amount of time learning
by BeetleB 8y ago
I've wanted to use this for a few years, and finally dived in this year.
The good: If you can wrap your head around it and spend a fair amount of time learning it, it is quite useful, and the claims on the web site no longer seem crazy. It's not my primary editor, but I can see I'll use this a lot (primarily an Emacs guy).
The bad: Very poor documentation. A lot of the stuff on the site is outdated (so examples won't work). In my experience, people on the mailing list will help, so it makes up for the poor docs - but it is kind of off-putting. There's a ton of stuff it supports that are mentioned nowhere in the docs.
Some hints: Learn how settings work, and dive into all the settings - you can do this from within Leo. You'll learn a lot more about Leo's capabilities that way (as well as make small tweaks to the pretty ugly UI). Changing a setting doesn't go into effect immediately - for that I think you can do:
M-x reload-settings (honestly forgot the command).
Some settings, though, involve quitting and restarting.
Also, it's not really a great editor. Its power comes from nodes and scripting. So become very comfortable with nodes, and try to learn scripting immediately. I'm still a beginner at the latter, and sadly the docs just suck. So I slowly try, ask, learn more, make my own notes, etc.
If I keep it enough to become much more knowledgeable, I'll probably end up writing a proper guide on using it.
It very much is similar to Emacs in the sense that everything is a command/function. So you can reprogram it to do whatever you want.