On Jan 12, 8:36 am, "Edward K. Ream" <[email protected]> wrote:
> I am going to add all the easy vim-related bugs to the list of things > to do before b2. That will delay b2 only a few days, and these bugs > really should have been fixed over a year ago. Leo's to-do list for > b2 now contains all the bugs broken out individually. After studying vim itself last night, I'm going to change my mind and delay this work until after b2. I don't want to distract myself until then. It looks like "doing vim right" in Leo is going to involve significant work. The more I study vim, the more I admire it's ideas, and the more eager I am to extend its ideas to Leo. But this will take significant work, and a new bzr branch. Leo's mode machinery is already both complex and inflexible. Of particular concern: commands requesting user input must be the last command executed within an @mode node. It's not clear to me that this restriction can be removed with the present structure of k.getArg. An entirely new approach may be needed. In short, it will probably be best to make haste slowly. I assure you that vim support will have top priority after Leo 4.7 goes out the door. 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.
