It's been a long time since I declared a quiet time for myself. It seems like a good thing to do right now.
During quiet time I'll defer responses to discussions here. The purpose of quiet time is to rid myself of day-to-day distractions, and instead focus on questions. Text editors like vim and emacs have two main components: A: Idiosyncratic machinery for adding and editing text. B: A set of commands. We spend a lot of time discussing A and B, and related implementation and efficiency issues. That's perfectly reasonable. However, Leo is bigger these topics. My goal during quiet time is to step back and look what can be done with Leo's existing machinery: - Leo's data structure, a DAG, including user data (uA's). - Leo's API, centered on c, g and p, including p.u (uA's). - Leo's plugins and importers. - Leo's VR pane. - Leo's commands, especially Leo-centric commands like the clone-find commands and outline-oriented abbreviations. I will be considering questions such as the following: - Might there be a more Leonine generalization of emacs-style macros? - Is there a way for me personally to get some of the benefits of vim without vim-like modes? The above two questions look like small beer. Bigger questions are on my mind: - Are there are important problems that could be addressed with Leo's unique features? - Are there tasks that Leo's users might want that might require significant additions to Leo's existing machinery. Finally, I'll be looking for even bigger questions, and especially juicy problems that Leo might help solve. *Summary* I'll continue to monitor this forum, but I'll defer most responses until quiet time is over. I'll ignore most implementation issues. Instead, I'll focus on Leo as seen by scripting-savvy users. 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/62a0f4b4-7921-4c18-88ba-c4f18e392088%40googlegroups.com.
