On Sunday, September 1, 2019 at 3:53:51 AM UTC-5, Edward K. Ream wrote: The aso.start method, and its helpers, now appears to recreate the required > initing of settings *exactly* as is done in Leo's startup code. *Subtle > bugs will abound if it doesn't*. >
Oh joy. There is a simple way around these difficulties. The command's startup code will make deep copies of the dicts needed to show setting accurately. The code that creates the summary outlines will use these copies, rather than the code created by the startup. This is a slight of hand. We definitely do want to do the full startup logic, so that, for example, abbreviations, key bindings, theme appearance, etc. etc. are as expected. But we don't want to bet that there are no subtle differences between the logic in the local file and the logic in the active outline settings file. This is a simple, sound plan to ensure that the active-setting-plan command will accurately show settings, even though it exists in a new commander. In other words, it satisfies both requirements I have just challenged Vitalije with. 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/0e488d30-c394-41e6-a5b1-c73216e00a85%40googlegroups.com.
