console.log scope

[zelivans]

When I use console.log in the developer console (F12 on Chrome), the text is logged into my snippet. Can it be fixed so that console.log logs to the correct scope (if used inside Klipse, log into the snippet, otherwise log to the regular console)?

[dmsnell]

Related to #194

While it seems like we can turn off console redirection this feature is still useful in the right scope. Ideally we can trap console statements without taking over the global console object.

Further, when interacting with multiple KLIPSE editors on a page I think it's unclear which one will get the actual log statements - I suspect there's a data race in "whichever editor loads last" gets the console messages.

Having each editor redirect the eval()'d console statements and appending the output to its container is great; taking over global is preventing some integration that I would like to do as it traps console statements from other parts of the website entirely outside of KLIPSE.

[workshub[bot]]

A user started working on this issue via WorksHub.