On Tuesday, June 8, 2021 at 5:50:40 PM UTC-4 Félix wrote: > Hi all :) > > First - make sure you ran 'npm install' in leointeg's project folder to > fetch any new dependencies that may have been updated since last time. > I finally realized to do this, but it took some time. It brought in a lot of things.
> > Second - (most important) specify how you want to start the server, > otherwise it's hard to help and give instructions :* There are 3 ways to > start the leobridgeserver while in developement* - (by vscode itself to > debug it while it runs, by leointeg itself using the command string in its > options settings, or starting it yourself in a terminal) after the release, > there will be only 2 ways (unless running in debug) > It's very hard to understand what the difference is. I tried the three ways offered in the "run" dropdown, but they always failed. > So to specify this, goto the debug view of vscode, (the triangle with the > bug) right at the top you have to choose what you want to debug (and what > will be started by vscode itself)* the extension, the server, or both*. > > If you want vscode to start the server , (*like in Edwards original post > in this thread I presumed from his description*) then it's vscode's own > python development settings that will decide how it starts it. (users using > v1.0 will not be using this method) So leointeg has nothing to do with it. > > If you choose to have leointeg start the server itself, choose "run > extension" only, in the top debug dropdown. (equivalent with the real > finished product,) then start with F5, then, in the extension host that > just popped and runs leointeg, open the leointeg settings panel and select > 'start server automatically', (and later come back here to also set the > python launch string if you need something other than 'python' on linux and > 'python3' on windows. (you may need to close the extension host and hit F5 > again to restart after setting the options if you want to actually see > leointeg start it by itself. ) > F5 did work to start the extension, as you said. The F5 that wouldn't work for me (mentioned in my last post) is in the extension window, where I wanted to run an @file program. However, I seem to like using the arrowhead-like icon in the lefthand icon panel. It's the fourth one down. That gives you the view where you can select to run the "extension only" up at the left top. > Another (third) way to start the server, is to simply start the > leobridgeserver.py script in a terminal program of your choice. > This is what worked for me. I started leobridgeserver outside of vscode. Then I used the little "run" button next to the dropdown where I had selected "run extension". Running the server from within vscode just hasn't worked for me. vsc runs my python batch file but the server apparently does not start. Oh, yes, this is on Windows 10. > To access leointeg's settings (while running leointeg in the extention > host) use ctrl+shift+P to open the command palette and start typing leo > settings (or leo welcome) to access the leointeg options. (to set your > python command line option for when you want leointeg to start the server > itself) > > I know it wont help you, hehe, but on both my windows and linux machines, > everything works without any special settings / string with my vanilla > installations of python. (I'm not a python expert who has many > pythons/anaconda/etc...) > > *Note: the leointeg welcome/settings webview are not visible in your > regular window of vscode, because it's generated by leointeg - so its only > available and visible in the extension host window that opens once you > press F5. * > -- > Félix > > -- 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/c6ead6e6-3b8c-4c60-8c83-5b18b736abb0n%40googlegroups.com.
