Posting this just because I discovered a source of many bugs and felt giddy!
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! Follow along at https://github.com/boltex/leointeg/projects/1 and make sure to watch the tongue-in-cheek promo video https://www.youtube.com/watch?v=SYwlfdEukD4 I made a couple months ago if you havent already :) -- 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. -- 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/d69b9982-7b42-4839-9be5-f3249d077cb0o%40googlegroups.com.
