All right, it installed in vsc and it did open an outline. I saw a lot of errors like this:
reading settings in C:/Users/tom/.leo/workbook.leo TypeError: Cannot read properties of undefined (reading 'trim') at Ini_Importer.find_blocks (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1507413) at Ini_Importer.gen_block (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1508153) at Ini_Importer.gen_lines (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1511889) at Ini_Importer.import_from_string (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1512400) at exports.do_import (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1522910) at LeoImportCommands.createOutline (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1338218) at async AtFile.readOneAtAutoNode (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:955878) at async AtFile.readFileAtPosition (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:954544) at async AtFile.readAll (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:953359) at async FileCommands.readExternalFiles (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1151896) at async FileCommands._getLeoFileByName (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1151493) at async FileCommands.getAnyLeoFileByName (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1149953) at async LoadManager.openFileByName (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:937514) at async LoadManager.loadLocalFile (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:936309) at async SessionManager.load_session (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1439599) at async LoadManager.doPostPluginsInit (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:932259) at async LoadManager.load (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:931126) at async runLeo (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1807739) at async activate (c:\Users\tom\.vscode\extensions\boltex.leojs-0.2.0\dist\extension-node.js:2:1815070) at async u.n (c:\Users\tom\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:140:6255) at async u.m (c:\Users\tom\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:140:6218) at async u.l (c:\Users\tom\AppData\Local\Programs\Microsoft VS Code\resources\app\out\vs\workbench\api\node\extensionHostProcess.js:140:5675) On Sunday, December 10, 2023 at 10:06:13 PM UTC-5 Thomas Passin wrote: > I'm afraid I can't get started. The beta insists on opening a repo first, > but I can't figure out how to either find my own repos or to get > authenticated for Github. > > I'd rather start working on a .leo file that isn't in a repo at all. I'm > never going to have all my outlines in a repo, but I want to be able to > open them anyway. My personal, on-computer repo is Mercurial anyway, not > git, and I don't feel like trying to change everything in Mercurial over to > git. So I hope that leoJs can be convinced to work with mercurial if it's > not going to be able to work with individual outlines on my drive. > > I'll try with vscode next. > > On Sunday, December 10, 2023 at 8:43:15 PM UTC-5 Félix wrote: > >> [image: leojs banner1.png] >> 🚀*LeoJS Debuts!*🌟 >> >> I'm thrilled to unveil LeoJS 'beta' 0.2.0 >> <https://marketplace.visualstudio.com/items?itemName=boltex.leojs>, a >> JavaScript implementation of the Leo Editor, now reimagined as a VSCode >> extension. Building on the foundation of LeoInteg, LeoJS revolutionizes >> your coding environment by seamlessly integrating into VSCode. >> >> Available on the VSCode marketplace >> <https://marketplace.visualstudio.com/items?itemName=boltex.leojs>, or, >> for VSCodium <https://github.com/VSCodium/vscodium>, on the open-vsx >> marketplace <https://open-vsx.org/extension/boltex/leojs>. >> >> *Key Features of LeoJS* >> >> - Like its predecessor, LeoInteg, LeoJS employs VSCode's robust GUI to >> host a variety of panels and controls, offering a smooth and familiar user >> experience. >> >> - With its entire architecture in TypeScript, LeoJS operates directly >> within VSCode — no external servers or additional communication layers. >> This direct integration ensures faster responses and a more efficient >> workflow. >> >> - LeoJS introduces live JavaScript script execution, providing a >> dynamic and flexible scripting environment. This feature extends the >> versatility of Leo beyond its traditional Python-based framework. >> >> - The bulk of Leo's core and command classes have been meticulously >> ported to TypeScript in LeoJS. >> >> - Key plugins from Leo, such as quicksearch.py, nodeTags.py, and >> mod_scripting.py, are seamlessly integrated into LeoJS's core. >> >> *Web Compatibility* >> >> LeoJS isn't just for desktops. For the first time ever, run Leo as a web >> extension on vscode.dev, enabling direct editing of Leo documents in >> online repositories. >> >> ( See >> https://code.visualstudio.com/docs/editor/vscode-web#_opening-a-project ) >> >> Simply visit a GitHub repository, press '.' to switch to the VSCode web >> edition, install LeoJS from the extension panel, and you're set! >> >> For local document editing, the regular desktop version of LeoJS & VSCode >> remains your go-to option. >> >> *Using LeoJS alongside LeoInteg* >> >> For those who use both extensions, you'll notice distinct activity bar >> icons and panels for each. To avoid clutter in the explorer panel, LeoInteg >> will automatically hide when LeoJS's 'show-in-explorer' setting is enabled. >> >> *Join the Beta Release Journey* >> >> I invite you to be part of this exciting phase: Your feedback and bug >> reports <https://github.com/boltex/leojs/issues> are invaluable in >> refining LeoJS for a full release! >> >> Many thanks to Edward for creating Leo, and thanks to you, for trying it >> out and helping squash the remaining bugs! 😆 >> >> 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+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/91f4ddb9-136d-4923-9ccf-9dcc92ac561an%40googlegroups.com.
