Thanks, Felix. Now if we wanted to test out a code modification or addition, how would we incorporate that into an extension that VSC could load or install?
On Sunday, December 24, 2023 at 12:15:08 PM UTC-5 Félix wrote: > Hi Thomas, > > Great question -- Thanks for asking! > > Since LeoJS is a VSCode (or vscodium) extension, its source code is > compiled/minified somehow, and many other source files are omitted from the > final 'distribution' package. > > Therefore, the way to open and view LeoJS source files (or browse it's *Leo > source file* in Leo/LeoJS) is to clone the repo from > https://github.com/boltex/leojs, and look at the base of the project > folder for *leojs.leo. * > > [image: screen.png] > > This would be the equivalent of LeoPyRef.leo. (and if you're looking for > the equivalent of the base setting file, leoSettings.leo, its at the same > place, and named *leojsSettings.leojs*. > > Hope this helps! 🦁 > > Félix > > > On Saturday, December 23, 2023 at 10:54:43 PM UTC-5 [email protected] > wrote: > >> IOW, where or how do we look at Leo's code? Locations like *g.app.leoDir* >> are undefined. > > -- 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/88cd0619-692a-4935-9c08-a41bfd693bb2n%40googlegroups.com.
