If the list is long, maybe send all default leo base commands as a list to be kept, ensh leoBridge/leoInteg startup. ... and only send back on calling get-commands (alt+x when opening the minibuffer-palette) the list of (added/removed might have changed) custom commands/@commands that may exist at that point in time. (as the whole of the default base Leo commands is a big list and does not change)
if it makes sense? (just got out of bed i'm fuzzy) -- Félix On Saturday, July 18, 2020 at 1:18:33 PM UTC-4 Edward K. Ream wrote: > On Sat, Jul 18, 2020 at 11:38 AM Félix <[email protected]> wrote: > > On the branch I'm working on, I've already started the interface for the >> minibuffer and @commands usage : >> >> Alt+x Brings up a custom (fake) command pallette thats going to be acting >> mostly somewhat like the command pallette/Leo 's minibuffer. >> >> I switched working on something else because I lacked knowledge on the >> python's side of things to '"fetch all commands names" or "fetch all >> startin with string 'xxx'"... and "run-by-name"! >> > > Leo has several "master command" dicts that should help. > > So as a starting (or branching) point : here's a throwaway leo file >> containing only a "basic" leoBridgeServer outline" just to show you the >> function skleletons: >> > > I see. After a .leo file loads, a single call so a similar function could > return *all* the valid command names. > > I wonder whether there is a way to give vc-code all of Leo's commands > *dynamically.* Failing that, I wonder whether the startup code could > create package.json *dynamically*. > > Edward > -- 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/adff50ec-4992-47d0-b795-4396467834ben%40googlegroups.com.
