The mystery is solved and all is well (no error messages). Turns out I accidentally started my main Leo session from the Python install library instead of from my git clone. Then I opened LeoPyRef.leo. It was open when I closed Leo, so the next time I started Leo - from the git clone as intended - it re-opened all the previously open outlines. Except that the open LeoPyRef outline was still the one from the Python install tree, not the git clone. But of course, since I had opened the clone, I expected the outline to be the one in the clone tree. Talk about cognitive dissonance!
It took way too long for me to notice that the wrong outline was getting opened on every launch. I could have found out from the title bar of Leo's window, but how often do you actually read that? On Wednesday, August 31, 2022 at 11:47:58 PM UTC-4 [email protected] wrote: > Funny, I just launched another session and got the branch/changeset > numbers. I still get those wrong file paths, though. I start Leo with > python3 > -m leo.core.runLeo. > > On Wednesday, August 31, 2022 at 11:40:54 PM UTC-4 Edward K. Ream wrote: > >> On Wed, Aug 31, 2022 at 10:30 PM [email protected] <[email protected]> >> wrote: >> >>> I'm seeing the following error messages in the console today, after >>> updating devel from GitHub: >> >> >> Hmm. Not sure why you are having problems. I just did the following as a >> test: >> >> git clone https://github.com/leo-editor/leo-editor.git leo-editor-test >> cd leo-editor-test >> python launchLeo.py >> >> All seems well. I suggest you reinstall Leo using git clone into a new >> leo-editor folder: >> >> git clone https://github.com/leo-editor/leo-editor.git >> >> 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/219eb485-cb0f-4a96-9e0d-3b5f61ec2593n%40googlegroups.com.
