2.1PROD/EA2: Show Errors problems

Question

With 2.1EA2 (JDK 1.6.0_16), the "show errors" command still doesn't ever seem to report errors (long time problem for me - see 1.5PROD/EA3/EA2/EA1 - BUG: Show Errors for View says no errors when errors). As well as that, when trying to run a show errors statement, nothing appears in the statement output window (which it does open if it is not there already) and I get the following text to the logging page:
The following was not written to the Script Runner Result Window as the outputStream was closed:No Errors.
theFurryOne

Answer 1

At least 2.1 production has improved the display of the "No errors" message - this always appears in the statement output window. However, this functionality is still not working properly (at least compared to the SQL Plus command that it is meant to be an equivalent of).
In SQL Plus, the "show errors" (on it's own) displays the errors (if any) from the last PL/SQL object created in the current connection. However, additional parameters can also be used to display errors for any other objects. The first way appears to be the only way that SQL Developer treats any show errors command - even if using those additional parameters which should change which object the errors should be reported for.
As an example, the following code:
create or replace force view xxx_dummy_v
as
select d.fred
from   dual d
show errors view xxx_dummy_vIn SQL Plus, this reports the error in the xxx_dummy_v view (d.fred is an invalid identifer).
In SQL Developer, this same code reports "No errors", unless I have created PL/SQL objects in the same connection and the last one had errors, in which case it reports the errors from that last created PL/SQL object.
Is it possible to improve the functionality of the "show errors" in SQL Developer to match the same command in SQL Plus? If not, it would be better to have an error displayed in the statement output if you attempt to run show errors with any parameters, as they are ignored. Getting errors for package A when requesting errors for view B is just wrong.
theFurryOne