Talking with TL a few days ago I was reminded of importance of stability in Leo. Tom said he spent considerable time checking that new features of Leo didn't break his code, especially regarding rst.
I assured him that I never make changes that knowingly break existing code without good reason. Still, the conversation surprised me. For so many years I have been focused primarily on adding new goodies to Leo. I was good to be reminded that many people use Leo for production work, and those people do now want unpleasant surprises. I think that keeping Leo's core unchanged (compatible) is the reasonable policy here. We can tolerate almost any changes to Leo's plugins. True, Leo 4.8 and 4.9 contemplate substantial changes to Leo's core, but those changes should have little or no external effect: 4.8: Lots of work fixing vim-related bugs and adding *compatible* new key-related features. 4.9: A rewrite of autocompletion, keeping the api and the user experienced unchanged as much as possible. 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.
