On Monday, October 8, 2018 at 4:58:28 AM UTC-5, Edward K. Ream wrote: > - Why must we reload settings every time Leo starts?
On my machine, detailed experiments (in the config branch) show that caching settings does not improve Leo's startup time. Like all caching code, the new code was difficult and fragile. Imo, caching definitely should not be done by default. Leo would effectively break if the cache were cleared. Yes, it would be possible to test for cached settings, but my prototype did not do so, and the extra code would be even more complex. Finally, two new command-line options would be needed. --save-settings would ask that settings be cached on exit, and --load-setting would ask that cached settings be loaded on entry. The wrong settings would be used unless settings for *only one file *were cached. *Summary* Caching settings would very likely be a step backward. I am not going to do it. Instead, recent revs in devel omit most signon messages in the console. I never pay attention to them, and they appear in the log pane anyway. However, the 'reading settings' messages do appear if --trace-startup is in effect. This command-line option also prints the total startup time. It's about 2.5 seconds on my test file. 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
