RFE: Collapse/Expand support for exceptions in console output window

Arik Kfir wrote:

Thought it might be a nice feature to be able to have collapse/expand
support for exceptions in console output window (like folding in the
source editor).

I would prefer to see jetbrains expend the resources to implement that functionality in a
built-in log viewer/receiver.

If you are currently dumping stack traces to the console window, then you should really be
using a logging utility like log4j or java.util.logging to make it more manageable.

well actually I only log to log4j ofcourse, but my log4j is configured to dump to system-out while
developing (and in production to a file). But your advice sounds good - I haven't tested the log
viewer yet.

Indeed I wouldn't mind having that only in the log viewer - and if so, I'll switch to it! :)

Tim Haley wrote:

Arik Kfir wrote:

>> Thought it might be a nice feature to be able to have collapse/expand
>> support for exceptions in console output window (like folding in the
>> source editor).

I would prefer to see jetbrains expend the resources to implement that
functionality in a built-in log viewer/receiver.

If you are currently dumping stack traces to the console window, then
you should really be using a logging utility like log4j or
java.util.logging to make it more manageable.

Arik Kfir wrote:

well actually I only log to log4j ofcourse, but my log4j is configured
to dump to system-out while developing (and in production to a file).

I find dumping to a file during development to be rather useful. It's
nice to have a non-temporary record of what went wrong, especially if
you have a lot of debug output.

Ciao,
Gordon

--
Gordon Tyler (Software Developer)
Quest Software <http://www.quest.com/>
260 King Street East, Toronto, Ontario M5A 4L5, Canada
Voice: (416) 933-5046 | Fax: (416) 933-5001

Gordon Tyler wrote:

I find dumping to a file during development to be rather useful. It's
nice to have a non-temporary record of what went wrong, especially if
you have a lot of debug output.

I usually log to a socket appender and use Chainsaw V2 to watch the output. That gives me
the most flexibility in being able to sort through the logs and not miss something important
while filtering out the noise.
I have also used the Log4jMonitor plugin, but it is a little buggy, not overly user-friendly
and not currently being supported by anyone.
If JetBrains makes the new logging support applicable to more run configurations, maybe that
will be the ticket. See http://www.jetbrains.net/jira/browse/IDEADEV-222