Having Leo play well with others, both programs and people, is likely to be my focus in the near-to-mid-term future.
However, playing well with others does not mean rewriting others :-) First on the list is completing the documenting for autocompletion, so that Leo can become a first-rate IDE for Blender. Another "new" direction will be to use Leo to improve Leo's own code. Better vim-like bindings is high on the list. Perhaps I'll use Leo's new c-to-python command to study the vim sources... In general, it would be good to build in support for running external tools more easily from Leo. The IPython bridge remains a mystery to me. I'd like to make sure that the bridge works with the latest public version of IPython. Documentation is an important part of playing well with others. First on the documentation list is folding all the items from the "What's new in Leo" sections into Leo's main documentation. I should also highlight the most important and least documented of Leo's minibuffer commands. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
