Show stdout and stderr messages in a separate Console window #97
Comments
ctrueden
added a commit
that referenced
this issue
Jan 8, 2015
This reverts commit 2447ea0. This address Fiji bug 984: http://fiji.sc/bugzilla/show_bug.cgi?id=984 As well as several complaints on the mailing lists. It seems that many people use the ImageJ1 Log window for macro output, and conflating anything else into that window disrupts workflows. So, we will need to find another way to preserve vital information dumped to stdout and stderr. Perhaps a dedicated Console window? It should probably not appear automatically though unless an exception is detected. See issue #97 for details.
|
Fixed forever in 0956b34! No more messages to /dev/null! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Messages to stdout and stderr always need to be logged somewhere. Let's create a separate Console window for this. (Conflating it with the ImageJ1 Log window caused numerous complaints—e.g. Fiji bug 984.)
Would be best to not make the Console window visible when it receives any ol' output, but only when an exception appears. That way, users do not miss vital stack traces, but are not bothered by things like the Bio-Formats log messages.
The text was updated successfully, but these errors were encountered: