On Friday, September 20, 2019 at 5:33:31 AM UTC-5, Edward K. Ream wrote: Sounds like a worthy bug. Thanks for sharing it with us. >
A few more thoughts. 1. A good goal would be to drop into the debugger (g.pdb) when the bug happens. Easier said than done, surely. If you *can* do this, then you can look around at the whole environment. I suggest using g.printObj(x) on complex x. 2. I wonder whether this bug could be related to #35 <https://github.com/leo-editor/leo-editor/issues/35>, which was the result of timing issues when opening multiple .leo files from the bridge. The fix is ugly enough that it might not be solid. 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/e454cce9-82dc-4192-8210-b592c92b8335%40googlegroups.com.
