I recently had a new PC built w/ Win10 at my office. After installing Anaconda3 as my Python environment and installing Leo from GitHub as usual, I was unable to get Leo to start beyond displaying the splash screen. After much gnashing of teeth and experimentation, I figured out what the problem was. I had copied my original desktop shortcut to Leo, which included the two command line options; --session-save and --session restore.
So, apparently, Leo will fail startup if there is no leo.session file, which doesn't get created until after a session is saved at least once. So, I had to run the launch with -session-save and *not* --session-restore first, then exit which creates the leo.session file. Then I could add back the --session-restore switch and Leo launched successfully as before. Would this be considered a bug or expected (though somewhat surprising) behavior? Rob......... -- 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.
