This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 62959

Summary:	[50cat] Display compilation error without use of mouse
Product:	editor	Reporter:	Milan Kubec <mkubec>
Component:	-- Other --	Assignee:	Milutin Kristofic <mkristofic>
Status:	RESOLVED DUPLICATE
Severity:	blocker	CC:	hmichel, jglick
Priority:	P2	Keywords:	A11Y
Version:	5.x
Hardware:	All
OS:	All
Issue Type:	ENHANCEMENT	Exception Reporter:

Description Milan Kubec 2005-08-24 15:56:19 UTC

[dev-20050824]

When working in editor almost everything is "reachable" by keyboard except
viewing compilation errors. We should provide some way how to show compilation
error to user without touching mouse. There could be shortcut to display the
error as a tooltip or we could dislay that error in editor status bar when user
is on the line with error.

Comment 1 Todd Fast 2005-08-25 14:11:12 UTC

I definitely endorse the idea of using the status bar to show the error message
for the current line.  +1

Comment 2 Jesse Glick 2005-08-25 16:28:41 UTC

Yes please. This would make everyday editing noticeably more pleasant.

Consider using main status bar if editor status bar is disabled.

Comment 3 Milan Kubec 2006-01-04 08:25:44 UTC

*** Issue 70956 has been marked as a duplicate of this issue. ***

Comment 4 Jesse Glick 2007-08-08 16:24:11 UTC

Seems that Alt-ENTER can be used for this purpose in NB 6? Not as nice IMHO as having the error be automatically
displayed in the status line, but better than nothing.

Comment 5 Jesse Glick 2008-02-13 10:12:32 UTC

Alt-ENTER does work once you are on the line, though I would rather this info be displayed automatically. Does not help
to jump to the next error/warning but that is another issue.

Comment 6 Jesse Glick 2012-05-03 15:38:14 UTC

(In reply to comment #0)
> we could display that error in editor status bar when user
> is on the line with error.

See fix of option #3 of bug #203810.

*** This bug has been marked as a duplicate of bug 203810 ***