LeoInteg 1.0.24 Released!

[Félix]

New Commands in LeoInteg 1.0.24 🧰🛠️  

This release brings a couple of handy new commands, originally suggested by Edward and added to LeoJS a few weeks ago. With the recent release of Leo 6.8.5, it's now possible to support them fully in LeoInteg — so here we are!  

• Go to Line in Leo Outline – Available from any Editor context menu other than a body pane. If the file isn't already in the outline, you'll be prompted to import it.

• Import into Leo Outline – Available from both Editor and Explorer context menus for files in VSCode's workspace.
  

Those commands are the first ones usable in the explorer and editor's context menus, outside of Leo's body or outline panes. Here are some screenshots:

  

Also, g.es will now automatically show the log pane when running user scripts or @button actions — making it easier to see what's going on.

You can get this update via auto-update, or download it directly from the VSCode Marketplace and the Open VSX Registry Marketplace for VSCodium!  

If you have any comments, encounter any issues, or have suggestions for future updates, please don't hesitate to share them on the GitHub Issues page.

A heartfelt thanks to everyone who’s taken the time to contribute ideas or feedback! It makes all the difference. 🦁

Félix

[Viktor Ransmayr]

Hello Félix,

I have tried to install / upgrade LeoInteg to this version in a Fedora 41 VM.

I have upgraded Leo to version 6.8.5 - and - installed 'websockets' version 15.0.1 !

When I start VS Codium with the upgraded extension I receive the following error msg:

<Log>

    Launching server with command: python3 /home/user/.local/lib/python3.12/site-packages/leo/core/leoserver.py --port 32125

    Starting LeoBridge Server 1.0.11 (Launch with -h for help)
    LeoServer: init leoBridge in  1.7 sec.

    ###

    Error - Cannot start server: Leo server exited with code 1
 

</Log>

Since I knew this setup was running in the past in a similar environment on my side I searched a bit on the Internet & found out that the asyncio implementation in websockets has been rewritten [1 & 2].

Could it be that LeoInteg version 1.0.24 does not work with websockets version 15 anymore - and - requires what is now called 'websockets.legacy' ?

With kind regards,

Viktor

---

[1] https://websockets.readthedocs.io/en/stable/

[2] https://websockets.readthedocs.io/en/stable/howto/upgrade.html

[Edward K. Ream]

On Tue, Jul 8, 2025 at 6:59 PM Félix <felix...@gmail.com> wrote:

New Commands in LeoInteg 1.0.24 🧰🛠️  

This release brings a couple of handy new commands, originally suggested by Edward and added to LeoJS a few weeks ago. With the recent release of Leo 6.8.5, it's now possible to support them fully in LeoInteg — so here we are!  

Thanks for keeping all the flavors of Leo in sync!

Edward

[Viktor Ransmayr]

Hello Félix,

Am Mi., 9. Juli 2025 um 06:44 Uhr schrieb Viktor Ransmayr <viktor....@gmail.com>:

...

You can get this update via auto-update

, or download it directly from the VSCode Marketplace and the Open VSX Registry Marketplace for VSCodium!  

If you have any comments, encounter any issues, or have suggestions for future updates, please don't hesitate to share them on the GitHub Issues page

I have tried to install / upgrade LeoInteg to this version in a Fedora 41 VM.

I have upgraded Leo to version 6.8.5 - and - installed 'websockets' version 15.0.1 !

When I start VS Codium with the upgraded extension I receive the following error msg:

<Log>

    Launching server with command: python3 /home/user/.local/lib/python3.12/site-packages/leo/core/leoserver.py --port 32125

    Starting LeoBridge Server 1.0.11 (Launch with -h for help)
    LeoServer: init leoBridge in  1.7 sec.

    ###

    Error - Cannot start server: Leo server exited with code 1
 

</Log>

Since I knew this setup was running in the past in a similar environment on my side I searched a bit on the Internet & found out that the asyncio implementation in websockets has been rewritten [1 & 2].

Could it be that LeoInteg version 1.0.24 does not work with websockets version 15 anymore - and - requires what is now called 'websockets.legacy' ?

To be absolutely sure that there is an issue, I performed a completely fresh installation of Leo 6.8.5 & LeoInteg 1.0.24 into a NEW Fedora 41 Test VM. - It still shows the same problem !

* Create Test VM & install Leo 6.8.5 into it - OK - See "Log-001".
* Start Leo for the first time outside of VS Codium - OK - See "Log-002".
* Start VS Codium & install 'LeoInteg' extension - OK - See "Log-003".
* Start Server - Not OK - See "Log-004".
*
* ---> Install 'websockets' from PyPI.
*
* Start Server - Not OK - See "Log-005".

<Log-005>

    Launching server with command: python3 /home/user/.local/lib/python3.13/site-packages/leo/core/leoserver.py --port 32125

    Starting LeoBridge Server 1.0.12 (Launch with -h for help)
    LeoServer: init leoBridge in 0.54 sec.

    ###

    Error - Cannot start server: Leo server exited with code 1

</Log-005>

With kind regards,

Viktor

[Robert-Felix]

Thank you  Viktor, 

I guess I'm going to have to check this new version of python websockets which is now the new standard!

This would affect 'new' users who install LeoInteg and this newer websocket version, and users who just happen to update it!

I'll try to fix the server to support this and will make it available as soon as possible.

Thanks again for testing those things out and for reporting them!! :)

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 leo-editor+...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/leo-editor/CAAeSrGJH42D29GShHgdN6yGeLNS8sNMeBeKt1ADTP9t-FgE%3DrQ%40mail.gmail.com.

[Thomas Passin]

Remember that there may be users who use different versions.

[Thomas Passin]

Probably relevant:

https://websockets.readthedocs.io/en/13.1/

On Wednesday, July 9, 2025 at 12:17:28 PM UTC-4 Félix wrote:

[Félix]

Thanks! It doesn't look too bad,

I'll modify the server to look at the websockets version installed, and act accordingly to support the old and newer versions.

Félix

[Félix]

Thanks to Viktor and Thomas, a fix is ready !  (They provided a totally compatible legacy interface API, so the fix was relatively easy!)

https://github.com/leo-editor/leo-editor/pull/4389

Hopefully this websocket API change that was in effect since November 2024 did not scare away to many people!

If I was a new user, I know I would have been stomped by such a random error without any ways of knowing what was causing that crash!

Félix

[Edward K. Ream]

On Wed, Jul 9, 2025 at 3:52 PM Félix <felix...@gmail.com> wrote:

Thanks to Viktor and Thomas, a fix is ready !  (They provided a totally compatible legacy interface API, so the fix was relatively easy!)

I have just merged the fix, PR #4389 into devel.

And commit 8e19587 suppresses a mypy complaint.

Edward

[Thomas Passin]

How can the vsc settings be arranged to launch LeoInteg from a virtual environment? The details will probably be different for Linux vs Windows.

[Viktor Ransmayr]

Hello Thomas,

Am Fr., 11. Juli 2025 um 17:46 Uhr schrieb Thomas Passin <tbp1...@gmail.com>:

How can the vsc settings be arranged to launch LeoInteg from a virtual environment? The details will probably be different for Linux vs Windows.

At the moment this does not work. - I have created a GH issue for that a while ago. - See

* https://github.com/boltex/leointeg/issues/299 

With kind regards,

Viktor

[Félix]

Thanks for your patience about this issue. I've started working on it now and propose a solution here after learning more about python venv.

https://github.com/boltex/leointeg/issues/299#issuecomment-3066468352

Félix

[Viktor Ransmayr]

Hello Félix,

Am So., 13. Juli 2025 um 05:33 Uhr schrieb Félix <felix...@gmail.com>:

Thanks for your patience about this issue. I've started working on it now and propose a solution here after learning more about python venv.

https://github.com/boltex/leointeg/issues/299#issuecomment-3066468352

I have been offline during the weekend.

I'll start reading about your proposed solution tomorrow & provide feedback.

With kind regards,

Viktor

 

[Viktor Ransmayr]

Hello Félix,

I'll start a new thread for that & post some findings from my side.

I'll do it in the forum, because I assume that more people (with venv experience) read it, than if I post it in the issue ...

With kind regards,

Viktor