On Mon, Mar 23, 2020 at 11:09 AM 'Marcel Franke' via leo-editor < [email protected]> wrote:
> Both solutions seems to be flawed as none of them is filtering by language. Glad you brought this up. Using c.atFileCommands.stringToString means implies that everything in p.b applies to the desired language. In contrast, using g.getScript calls g.extractExecutableString, which does the filtering you desire. Depending on your outline, and your outline's settings, using stringToString may allow the user to avoid @language directives, while using g.extractExecutableString is more flexible. There are pros and cons each way. > Is this uncommon in Leo community? I often have nodes with multiple mixed languages or mixed plaintext and code. It's common within LeoDocs.leo. There, @language rst and @language python are often intermixed. 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/CAMF8tS2SjWtKsi3ctur63hFA20eyDQXdg2hg2E-iRfbyLdYAyw%40mail.gmail.com.
