Thanks for the suggestion. However, I get the same result using your command, which is nothing happens.
Rob... On Friday, October 2, 2020 at 2:22:07 PM UTC-4 [email protected] wrote: > I always use the command python -m leo.core.runLeo. This lets me avoid > problems with paths to any special launchers, and just runs the actual code > directly. If I want to run from my Github repo, I first set the PYTHONPATH > environmental variable to the top of the repo first. > > As for the command you use, in its exact form your current directory would > need to be the same as the directory that launchLeo.py is in. The ".\" > does nothing useful. > > My installation of Leo 6.2 final using the Windows installer does not even > have a launchLeo.py file. That might be what is happening to you. > > Just use my command (above). You won't need to cd to the starting > directory, or add its location to the path, so it's easier and more > reliable. > On Friday, October 2, 2020 at 12:19:53 PM UTC-4 Rob wrote: > >> On just one of my Windows 10 PCs, Leo no longer starts (other PC works >> fine). Up until recently, this command line started Leo as expected: >> >> python.exe .\launchLeo.py >> >> Now, it just goes to a new command line with no error messages or >> anything. I tried various command line options with no success. The Leo >> version was updated on 7/2/2020, then again today from GitHub. >> >> Any ideas why or how to fix? >> >> 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 view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/1dd2bdda-eb0e-4a91-a870-ec794f19e4ban%40googlegroups.com.
