I wrote all of leoInteg without knowledge of the 'wrapper'... only using p and v nodes. setting 'bodies' etc... Turns out some commands pickup selection (and current body text) from the wrapper instead of the v nodes body content. (execute script, ectract, extract name , etc...)
The wrapper is set by leo when changing selection, this explains why some commands started working after having navigated the tree at least once.
anyways - feels good to have an illumination concerning an API you didnt read all the way though - like building an ikea furniture piece without reading the manual, kinda, oh well... hehe
So I'm finally seeing the end of the tunnel for issue #39, hopefully switching to #107 soon, to finally release a first version on the vscode 'market!
--
Félix
p.s. Although we're in 2020, It's not officially 'the future' until popular programmer editor technology has standard DAG/literate features somehow available!
p.p.s. I'm on it.