On Wednesday, November 20, 2024 at 10:38:09 AM UTC-5 Edward K. Ream wrote:
On Wed, Nov 20, 2024 at 9:35 AM Thomas Passin <tbp1...@gmail.com> wrote: I do not believe a word of your analysis. There is something wrong with your installation. Then you had better think again. 1. The exact same behavior happens on my Linux EndeavourOS VM. I just checked it. 2. My statement that the starting argument of -m leo.core.runLeo gets changed in *sys.argv* to leo\core\runLeo is a fact. It seems that we are discussing two different issues: 'restart-leo' vs starting Leo. They are closely related. restart-leo cannot know if Leo was started using py -m or not. Using py -m leo.core.runLeo gives a different result than py leo/core/runLeo.py if the working directory is leo-editor. The restart-leo command can't know which way Leo was started based solely on sys.argv. So it constructs the arguments for subprocess.run in a way that unfortunately causes runLeo.py to misbehave in the case that the starting directory is leo-editor. Therefore runLeo.py should be changed so that it no longer misbehaves in that particular case. Now that was analysis based on facts. I'll continue to investigate. 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 visit https://groups.google.com/d/msgid/leo-editor/eb849218-24c1-4345-acbc-287a744d5c13n%40googlegroups.com.
