Leo 4.7 and Robin Dunn's, "your mission, should you choose to accept it"
Edward K. Ream
http://groups.google.com/group/leo-editor/browse_thread/thread/4f76a0f57759aba
continues to be one of the benchmarks for Leo.
Leo 4.7 went out the door today. It contains many important
improvements, but few directly related to Robin's important post.
That doesn't mean Robin's post is irrelevant, but it does mean that
other considerations were more relevant :-) In particular, Leo passes
all unit tests with Python 2.6 and Python 3.1.
Leo 4.8 will concentrate on better support for vim-like bindings. As
a happy side effect, this will make Leo compliant with almost all
unfinished aspects of Robin's mission.
There are two major items from Robin's list that are incomplete in
Leo:
* The Kill-Ring. Leo does have a kill ring. The vim work will fix
discrepancies between how Leo, emacs and vim handle the kill ring.
* Good keystroke macro recording and the ability to save and load
keystroke macros. This happen as part of support for vim's "dot"
command. To some extent, Leo's execute-script command compensates for
wimpy macro support, but I'd like to do better.
The following could be done easily using Leo's @command or @button
features. There doesn't seem to be much demand for them in Leo, but
I'll list them here for completeness.
- Flexible build/grep commands.
- Interactive diffs, merges and applying of patches.
- Able to be a front-end for gdb. (Leo has a plugin to do this).
- Able to be a front-end for CVS, SVN, etc.
- Have a built-in psychotherapist or be able to play towers of
hanoi. ;-)
As always, I invite you all to try Leo, and to ask for features that
would be important to you.
Edward