I'd like to propose a sprint to discuss Leo 5.6. This should happen only after Leo 5.5 final goes out the door. This could be a virtual sprint, conducted entirely on leo-editor or #leo, or an actual sprint, perhaps in Ashland, WI or Superior MN.
There are both design and coding issues to be discussed. The main question is what do we want Leo 5.6 to do, and why. I am not interested in chasing after org-mode features, unless people really want them. In particular, emulating org-mode tables (including its spreadsheet features) seems like a lot of work. Several new features do stand out: - Better integration with .org files, say by supporting .leo.org or org.leo files. - Replace attrib_edit by p.drawers. <https://github.com/leo-editor/leo-editor/issues/414> - Support for pyzo's client/server based shell. It this needed? Do valuespace or python_console plugins suffice? I suspect pyzo's architecture is better, but I'm not sure how much better. And any other topics you might want to discuss. Yes, I've declared this to be quiet time, but *short *comments will be welcome now. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to leo-editor+unsubscr...@googlegroups.com. To post to this group, send email to leo-editor@googlegroups.com. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
