Let me spell out a little more thoroughly how my system is set up. Python 3.9 is launched with "py". I have one repo with Leo, and another with *leointeg*, which I pulled from Felix's yesterday. I'm using the *leointeg* code from the clone of Felix's repo, not from the Leo repo.
To run Leo using the code in the *devel* branch, I have created a little batch file named *py-leo-git.cmd* to set PYTHONPATH first: @set PYTHONPATH=c:\tom\git\leo-editor py %* This batch file is on the system path. I set the python command for *leointeg* to be *py-leo-git* (do *not* include the .cmd extension). This works for running *leointeg*, but not for starting the server. On Wednesday, June 9, 2021 at 8:57:34 AM UTC-4 Edward K. Ream wrote: > On Wed, Jun 9, 2021 at 7:27 AM tbp1...@gmail.com <tbp1...@gmail.com> > wrote: > >> Felix, I had already worked through your various screens before I finally >> got leointeg working. The only way I could get it to run was by starting >> the server externally, in a console window. Just now I manually started it >> in a terminal window within vscode and that worked (as expected). It is >> only having vscode start the server automatically that fails. > > > Hi Thomas, > > Thanks for this. Starting the server manually is a great idea. However, > leo is not on sys.path (on purpose, in my installation), so I must start > the server from the leo-editor folder with: python -m leo.core.leoserver. > This at least does work. > > Still having trouble connecting to the server after launching leoInteg. > > Within Leointeg I pointed leointeg setting to <full path to>leoserver.py. > The setting is in the panel with the big Leo logo on it. Sometimes I have > trouble finding the panel! > > When I attempt to start the server from leoInteg I get a traceback in > leoserver.py at line 24: > > Error - Cannot start server: stderr: Traceback (most recent call last): > File "c:\leo.repo\leo-editor\leo\core\leoserver.py", line 24, in <module> > > Line 24 is: from leo.core.leoNodes import Position > > This is (I think) expected because on my machine leo is not on sys.path. > > Perhaps leointeg should add leo to sys.path (if necessary) using the path > to leoserver.py. Or something like that. > > One last comment. There seem to be at least 3 separate places for > settings, not counting the User/Workspace distinction. Félix may have said > one would go away when leoInteg becomes an official plugin. Things are > pretty confusing right now, which to repeat may be a good thing, because we > all get to be newbies :-) > > 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 on the web visit https://groups.google.com/d/msgid/leo-editor/a566995e-1156-4b83-8cf7-a7c1c01d02f9n%40googlegroups.com.
