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. I put a print statement into the code to see (I forget whether ".py" gets appended). 3. My statement that py -m leo.core.runLeo acts differently from py leo/core/runLeo.py if the working directory is leo-editor is a fact. To illustrate using that same Linux VM, and running in a venv: (leo) [tom@tom-endeavour leo-editor]$ python3 leo/core/runLeo.py *Leo 6.8.0* Python 3.12.7, PyQt version 6.7.2 linux (leo) [tom@tom-endeavour leo-editor]$ python3 -m leo.core.runLeo *Leo 6.8.3-devel, devel branch, build 9862614477* 2024-11-16 08:56:31 -0600 Python 3.12.7, PyQt version 6.7.2 linux 4. The *restart-leo* command uses *sys.argv* to construct its subprocess.run() arguments. These things are facts, not my analysis, and not my installation quirks. -- 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/81ceb5d9-e3b5-465d-8017-32fcfe7d7f74n%40googlegroups.com.
