I see two main tasks for Leo 4.8: 1. Cleaning up the code. As usual, this kind of task should occur early in the release cycle.
I plan improvements to the caching code, to configuration logic and to the related logic that handles Leo's list of recent files. There are a few minor bugs that will be fixed too. I may create one or two short-lived branches for these. Or not. 2. Better support for vim and vim bindings. This is the major task of Leo 4.8. Most of this projects amounts to bug fixes, but some of these fixes will likely entail substantial changes to Leo's key- handling logic. This task must be done in a separate branch because it is both experimental in nature and potentially disruptive to Leo's operation. This branch may exists for several weeks before being merged into the trunk. There are other items on the to-do list for 4.8, but these are the most important items. Only these items are guaranteed to appear in 4.8. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To post to this group, send email to leo-edi...@googlegroups.com. To unsubscribe from this group, send email to leo-editor+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/leo-editor?hl=en.
