Despite what you say, I suggest keeping this option as a do-nothing option. No "fix" need ever be issued, or at least not until it is devised and convenient. Leo could print a deprecation message to the (error) console or log pane, or a message saying that caching is no longer used. Why break anyone's scripts without a good reason?
On Monday, June 25, 2018 at 9:10:25 AM UTC-4, Edward K. Ream wrote: > > The --no-cache no longer exists in the fast-read branch. This means that > Leo will fail to load if a startup script/.bat file uses --no-cache. > > I hope this will not cause great confusion when merging fast-read into > devel. I can see no perfect way to avoid these initial troubles. For > example, retaining --no-cache as a do-nothing option simply postpones the > fix. > > 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.
