On Tuesday, November 19, 2024 at 1:44:08 PM UTC-5 Thomas Passin wrote: I have tracked down what is happening but I don't know why. The problem is not with the restart command, it's with the runLeo.py module. It runs a different version of Leo, and even a different version of Python, depending on how it is invoked even though you would swear the results should be the same. Details are in the issue I just filed:
https://github.com/leo-editor/leo-editor/issues/4199 The reason that this problem has been showing up with the restart-leo command is that the launch command that is captured by sys.argv is NOT always that same command that launched Leo in the first place. The case that occurs for me is that I launch Leo using py -m leo.core.runLeo but sys.argv reports that argument as leo\core\runLeo (IOW, no longer using -m but just sys.executable leo\core\runLeo.py). It is exactly this difference that runLeo handles differently. -- 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 visit https://groups.google.com/d/msgid/leo-editor/d13b7b75-91b1-4771-ad3e-ce3f77d4bac9n%40googlegroups.com.
