Hmm... Choosing which python to use in vscode says to me you want to start the leobridge server via the vscode debugger (see debug panel, open top dropdown and choose 'run both') which renders the 'auto start' setting via leoInteg setting totally superflous in that case, and should be kept disabled, otherwise it will also try to start a server via node's "child.spawn(w_pythonPath, w_args);" (see serverManager,ts line 57) and you will get the "port in use" message.
Until this extension is released as a compiled package, for convenience, there are 3 different ways to start a leobridge server with leointeg. I realize I should clarify and document this, because what I gather from reading Matt's and Ar-Jan's is that I cannot determine which of those 3 ways they are going for at any given time. And mixing them up doesn't help running smoothly... Seems that this concept is not taken into account and its my fault to not having made all that crystal clear in the documentation. I'm finishing some other stuff and I will adres this in more details later. I just wanted to state the above real quick bluntly while i'm thinking about it. ok back to work now I'll give more updates tonight. -- Félix On Monday, July 6, 2020 at 12:41:28 PM UTC-4, Matt Wilkie wrote: > > > I just noticed you ran "npm audit fix" after running "npm install" so i'm >> not sure what dependency might have been raised to a version that might be >> problematic. >> > > Interesting. The first time I ran `npm install` in red text it reported > 320 vulnerabilities 70 of which were severe. (I neglected to capture the > log, so the 70 number is not exact.) > > I removed `leointeg\node_modules` and ran npm install again. This time it > reported only 11 low severity vulnerabilities: > > added 1034 packages from 542 contributors and audited 1104 packages in > 47.144s > > 17 packages are looking for funding > run `npm fund` for details > > found 11 low severity vulnerabilities > run `npm audit fix` to fix them, or `npm audit` for details > > > After this there is no change to the previous reported behaviour. > > >> Also, (as stated elsewhere), I also forgot to mention Leo's devel branch >> should be used with Leo, for multi-file support, until it's next release. >> > > Good to know. I am using Leo devel branch with leointeg, but heretofore > that was by habit and not intention. ;-) > > > Many thanks again! >> > > You're welcome. Thanks for introducing me to vscode. Before now I had > ignored it as I'm happy enough with the tools I know (Leo, Notepad++, > Pyzo). Vscode has much to recommend it, and I'm happy to be exploring that > first hand. > > -matt > -- 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/324063ca-2050-49a8-8e91-0b113f22abbao%40googlegroups.com.
