I was originally using devel in leo-editor, and master in Felix's repo. I see what you see in the "Output" tab in vscode when the extension starts. One caution - whenever I shutdown the extension (or it shuts down by itself), I cannot get it to show up when I run it again. vscode goes through the motions but the Leo icon never appears. I have to close vscode and restart it. On top of that, closing the extension also closes the leobridgeserver. So after a shutdown, you have to:
1. Restart the leobridge server; 2. Restart vscode. Hopefully Felix will be able to fix 1) - so that vscode will successfully launch the server - and 2) is probably a good idea so that we don't end up with forgotten zombie servers lying around. On Wednesday, June 9, 2021 at 6:16:16 PM UTC-4 Edward K. Ream wrote: > On Wed, Jun 9, 2021 at 5:11 PM [email protected] <[email protected]> > wrote: > >> When I look in the felix-server branch, leoserver.py is only an http >> server, not a websocket server. Which branch of the leo-editor repo are >> you working with? Neither the *felix-server* nor the *devel* branches >> contain leobridgeserver.py. So, as far as I can see, it is not possible to >> run leointeg without using leobridgeserver from Felix's repo. >> > > I'm in devel, for Leo. I'm in master for leointeg. I pointed leoInteg to > leobridgeserver.py in the leointeg folder. > > I'm hoping this kind of confusion won't be possible when leoInteg is a > real plugin. > > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/3fe880ac-df3a-40fc-9ff7-bd587f08ac61n%40googlegroups.com.
