I have no ability to answer the "why not" and doubt anyone here does.  While I cannot be sure what you are trying to describe, if it involves the compiler error window I have found that you can hover over the error and it will appear as a tooltip displaying the whole error.

It could help to better understand your problem if you include screenshots.

While you might prefer to have it your way, I am sure there are others who prefer more information rather than less, which is probably why they did it the way it is done, though I can't understand why they have it falling out the area and not wrapping instead.  Still, being able to see the entire message by hovering it is sufficient to get the information you want to see and it doesn't take much time/effort to do it.

I would like to see better error reporting myself, with more information, such as the ones that involve file loading errors where they won't tell you the name of the file that is causing the problem.  Or then there's the 1009 errors where they say an object is null, but you have to do your own research to find out which one it is.

copy the error and paste the error message into a text document that you can manipulate to suit your needs.

for compiler errors, you should be able to double click the error and be taken to the line of problematic line of code.  but if you don't recognize the error type in the panel, you'll still need to drag the description header to view the complete error text.

so, i don't think you can customize that panel to do what you want.  however, you probably could build a custom  panel that does what you want but you'll need to use jsfl and that might be more work than it's worth for you.

you're welcome.