I suspected it might be related to the 'forcePythonSentinels' line, and digging around I wasn't able to find out enough about that parameter (argument?) to understand what was happening (looked in leoPyRef.leo and a few other places). I will look around some more using your clues. As for the issue itself, it's really not a big deal, the easy workaround is to simply not have an @language in the node. However, it's possible that one of the downstream nodes will have that directive and I might miss data copied to the clipboard. Thanks for the pointer.
Rob... On Tuesday, January 29, 2019 at 3:38:35 PM UTC-5, Edward K. Ream wrote: > > On Tue, Jan 29, 2019 at 10:05 AM Rob <[email protected] <javascript:>> > wrote: > > > The weirdness is that if I place the @language directive as the first > line of the node and run the script, the clipboard is empty. I tried this > with several different @languages (tried tex, html, plain and c) and all > fail except @language python, which then works as expected. If I move the > @language directive to a parent node, the script works. > > g.getScript calls g.extractExecutableString(c, p, s), without any > 'language' kwarg, which explains the special case for @language > python. This is a bug. Knowing its source you could work around > it... > > 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 post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/leo-editor. For more options, visit https://groups.google.com/d/optout.
