yes. I was getting a lot of 'Error occured...' spam in the console which was not useful, so I added a little check to see if the output was meant to be the ps2 console and if it was, output the text instead of the error. I didn't know about the stdlogging option. In a way though, that log should always be on because the ps2 will always log to its stdout and so we don't want to spam the console with errors in that case (either that or silently swallow the exception for stdout).
The other thing is that the log files are only really flushed at the end of the program which is fine for post analysis - but you really want to see the ps2 stdout console in real time so you can see that it is working on something.
I'm not precious about this though, so change it as you see fit - it probably does not belong in this pull request to be honest but it crept into one of the commits.