leointeg 'dev' branch now updated for leo's 'devel' *Switch to the dev branch, run 'npm install' in the terminal to update dependencies and try it out ! *
Option replaced in the 'Settings' now about leo's home folder. Automatically finds /leo/core/leoserver.py ! yay! As a bonus, leointeg now will try more ports if the current default port, or the one specified in leointeg's settings, is in use when starting a server. So it's not bound to a single fixed the port nor a single instance - multiple vscode window will use subsequent ports/servers (up to 5 more for now) as a silly debugging tool/switch, i made it so that if *leobridgeserver*.py (with the old name) is present in /leo/core then it will use it for easy switching / testing purposes until leoserver.py is finished being rewritten correctly. It's temporary obviously. Many thanks to Thomas for his systematic approach and perseverance in pointing out all the stuff that didn't go smoothly on a typical machine for a 'new' leointeg user! This is most valuable input that really helps things move forward! 🦁 leointeg now activates after the vscode window's ready event instead of checking if there's a leo fine in the workspace or being switched to the 'Leo' view in the activity bar. -- 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/dc4afc54-d643-417a-b895-6a508de5e476n%40googlegroups.com.
