On Sat, Jul 4, 2020 at 2:10 PM Félix <[email protected]> wrote: > In Leo, print does nothing as far I as I can tell. (i've wondered since 2002 when i discovered Leo why print is not redirected to g.es by default) ...
Both print and g.trace print to the console, provided that you run Leo from a console, which I always do. > In leoInteg, print outputs on the stdout as would any script., so it's visible in the leobridgeserver.py terminal output. leoGlobals.py defines the g.RedirectClass class and several convenience functions. These redirect g.es to the Leo's log pane. At present Leo's bridge calls neither g.redirectStderr() nor redirectStdout(). It may be possible to do that from the leoInteg end, but if not I could add more keywords to BridgeController's ctor to do the redirection. I do see Leo's log pane in vs-code, so I suspect just calling g.redirectStderr() or redirectStdout() should suffice. 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/CAMF8tS2EQyEkYC5e9A-kpRYQQM99u9QZTb0htV0PenuWepaaOw%40mail.gmail.com.
