🚀 LeoJS 1.0.11 Released!

[Félix]

LeoJS 1.0.11 just landed! 🛸

This release brings a handful of new features suggested by Edward — including context menu commands you can now access outside the usual LeoJS panels, directly by right-clicking in the file explorer or editor view.

It also brings improvements to how LeoJS handles imports and script execution:

• Added "Go to Line In LeoJS Outline" (context menu in the VSCode file editor) — also offers to import the file if needed.
• Added "Import into LeoJS Outline" command (context menu in editor & explorer).
• Import commands now use relative paths when possible: When the Leo document and the file being imported are both inside the vscode workspace
• g.es now automatically opens the log pane when running user scripts or @button nodes.
• Scripts now run regardless of the write-script-file setting.

Available via automatic update or on the VSCode Marketplace, and for VSCodium, on the Open VSX Registry Marketplace!

Thanks for trying it out — and let me know what you think!

🔍 Want to learn more?
Check out the LeoJS documentation site for full details and examples.

🎥 New to LeoJS or curious about how it works in VSCode for the Web?
Watch the intro or feature-demo videos on YouTube to see LeoJS in action — including how to use it without installing anything locally!

Cheers,
Félix

[Félix]

  Well, that was fast! 😅 Found a bug right after pushing 1.0.11 — so 1.0.12 is out with a quick fix. 🔧  

[Edward K. Ream]

On Sun, Jun 15, 2025 at 9:07 PM Félix <felix...@gmail.com> wrote:

LeoJS 1.0.11 just landed! 🛸

This release brings a handful of new features suggested by Edward — including context menu commands you can now access outside the usual LeoJS panels, directly by right-clicking in the file explorer or editor view.

It also brings improvements to how LeoJS handles imports and script execution:

• Added "Go to Line In LeoJS Outline" (context menu in the VSCode file editor) — also offers to import the file if needed.
• Added "Import into LeoJS Outline" command (context menu in editor & explorer).
• Import commands now use relative paths when possible: When the Leo document and the file being imported are both inside the vscode workspace
• g.es now automatically opens the log pane when running user scripts or @button nodes.
• Scripts now run regardless of the write-script-file setting.

Thanks for this work!

Edward

[Thomas Passin]

"Import into Leo Outline As ..." didn't work for me from the shift-right-click menu.  I tried it in an .md file opened in the regular VS editor,  No dialog opened and nothing got imported. At the time I tried it, I had a new outline (no content and not saved) open in leoJS.

Identifier boltex.leojs
Version 1.0.12
Last Updated 2025-06-16, 13:04:45

[Robert-Felix]

Of course, like in the original Leo, using external files needs to be done in a 'saved' Leo document, otherwise there is no relation to a fixed path to figure out what the absolute path of an external file would look like. 

I should show a warning whan that happens! Thanks for trying it out and pointing out that behavior! :)

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/15c46c61-65f8-4adf-bc92-8f8612bb4194n%40googlegroups.com.

[Félix]

Oh, my bad, Leo actually uses the user's home dir as its current directory if the Leo document is unsaved & untitled.

Félix

[jkn]

I have mildly wondered about this situation when doing some experiments (with Leo) ... so thanks for the explanation/clarification.

    J^n

[Thomas Passin]

If one tries to import a file into an outline that has never been saved, IMO it should be imported and given its absolute path.  Then the unknown path of the outline won't matter. The user can convert it to a relative path if desired.  Or, maybe more useful, there could be a minibuffer command to convert an absolute to a relative path.

On Monday, June 16, 2025 at 7:56:22 PM UTC-4 Félix wrote:

[Félix]

>  If one tries to import a file into an outline that has never been saved, IMO it should be imported and given its absolute path.  Then the unknown path of the outline won't matter. 

Thanks Thomas, that's the exact conclusion I also came to.  :)

[Félix]

Thanks to Thomas's thorough testing and experimentation—specifically with reading and writing external files in new, unsaved Leo documents—several fixes have been made to both Leo and LeoJS in the past few days. These address issues related to the base directory used for resolving relative file paths during such file operations (e.g., @clean myFile.txt instead of @clean C:/myPath/myfile.txt).

As a result, I've released LeoJS 1.0.13, which includes these changes and fixes. They will also be included in the upcoming Leo 6.8.5.

I also want to thank Edward for the great command idea he suggested: integrating VS Code's context menu (in both regular file editors and the file explorer) with options such as "Go to line in outline" and "Import into outline".
("Go to line in outline" will offer to import with various @file node types if the file isn't already in the outline.)

These commands, combined with Leo's new default behavior of using relative file paths when importing external files, feel very natural and fun to use!

You can even try it instantly in vscode for the web by simply going to any repository on github and pressing the '.' dot on your keyboard to switch to the vscode web interface, (of course install LeoJS and create a Leo document), then click in vscode's explorer to open any file of your project, and then use the right-click context menu to see the command in the above screenshot.

These new features will be available in LeoInteg 1.0.24 as soon as Leo 6.8.5 is released.

Thanks so much for giving it a try—and for reporting any bugs or sharing feature suggestions. Your feedback really helps shape LeoJS! 😊

Félix

[Edward K. Ream]

On Sun, Jun 22, 2025 at 5:36 PM Félix <felix...@gmail.com> wrote:

've released LeoJS 1.0.13, which includes these changes and fixes. They will also be included in the upcoming Leo 6.8.5.

Excellent. I have just moved the release date for Leo 6.8.5 to Friday, July 4.

Edward