Adriweb and jimbauwens definitely talked to TI about the problem... to no avail, at the time of this writing.

...
We redirected the output of the print command to the console log of the integrated script editor. In retrospect, we should have maintained the print connection to stdout until the script editor console was fully implemented. Do you see value in continuing to send print output to stdout in addition to the script editor console?

Of course, I said yes.

I submitted a change request to reinstate output to stdout. I cannot guarantee the change control board will approve the change in time for the next software release. I quoted large parts of your email in the request.

Jim,

The change control board rejected the request. It comes too close to the end of the current development cycle. I'll add the change to the requirements for the next development cycle.

A bit later we asked how it was with the reintegration, and he answered this

I forwarded the request to turn print() back on in Lua to the product definition manager who defines requirements for Lua scripting. The feature should be a requirement for the next release. I'll check with him on the status of feature.

I wouldn't say "to no avail"

And I hope I don't lose my NDA because of this post.

No offense, but think that's just stinkin' thinkin'. Give them at least a chance ^^

There have been so many things that we wished, but they did not grant (and sometimes, had to grant ourselves), that we should not get ourselves excited until it's done

thats right
@Jim Bawens and what if TI included also a "listen()" to receive data from the RX serial?
EDIT: by data I mean text, of course... even char by char would be awesome...

Okay...
Do you think that it would be too dificult to be done by us, like the fixprint, maybe adding it to the fixprint code...

maybe I'll give it a shot in the christmas break