Leo's g, c, and p objects all belong to Leo, not Python or PyQt. if the
vscode object belongs to the codebase outside of leojs, I think that
g.app.vscode would be more appropriate and easier to use as a reminder of
who vscode belongs to.
On Saturday, September 2, 2023 at 9:49:43 PM UTC-4
Not sure what to decide for this so I thought of doing this quick survey! :)
When running scripts, (CTRL+B) Leo offers the g, c and p variables. I
obviously want to expose the vscode API from it's base object "vscode".
Should it be top-level along with c, g and p? or, be located at:
g.vscode
Hi all! :)
I've never used the @all directive and I'd like to test it properly with
both Leo and LeoJS.
If you happen to be familiar with those two directives, would you be kind
enough to make a Leo file that showcases one or two @file nodes that 'demo'
the usage (and difference in output)
