OK, a slight non-definitive update: Without changing any SW, it looks like I may have (accidentally) been loading a totally empty old .leo file, ie of 0 bytes length. I just picked this as an 'old, no-longer needed' test file, without looking at the contents.
Leo itself doesn't seem to have an issue with opening this file, it creates a 'null' headline etc. Might that have been the cause? I will try to take a better look later this w/end. Thanks, J^n On Saturday, October 1, 2022 at 2:48:14 AM UTC+1 Edward K. Ream wrote: > > > On Friday, September 30, 2022 at 3:59:21 PM UTC-5 Félix wrote: > >> you're right. I'll try to discuss this with Edward to make leoBridge more >> robust. (if the error is really about leobridge not handling something >> correctly under python 3.10.x) > > > I've just taken a look at leoBridge.py. The error likely arises because > the bridge is trying to open a non-existent file. In that case, > g.openWithFileName will return None. > > PR #2900 <https://github.com/leo-editor/leo-editor/pull/2900>prints an > error message (instead of crashing) if the file does not exist. I have not > tested the code. > > Please test the ekr-server-error-message > <https://github.com/leo-editor/leo-editor/tree/ekr-server-error-message> > branch and report whether the new code reports a missing file. Thanks. > > 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/e67586aa-0f74-48e3-99af-b3b64a97a8adn%40googlegroups.com.
