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.
dev build 200605031800 Mustang b81 I've reported this issue over a year ago and I believe it was closed as fixed but it seems to be back now. When I hit F12, the 2nd error is highlighted instead of the first. The problem is that if the user hits F12 while the file is still being compiled, the editor will not highlight the first error. Then the user hits F12 a second time, and now the editor will jump to the second error. I am expecting that if I hit F12 during compilation time, once compilation is over, F12 will be applied and the first error will be highlighted.
do you know the number of the original issue?
This is actually duplicated by issues #25062 and #48485, both of which were resolved as fixed and yet this issue either kept on coming back or it wasn't fully fixed the first time around.
Reassigning to new module owner Tomas Holy.
gili, is it still reproducible? It seems to work for me. Next Error -> CTRL + . (PERIOD) Previous Error -> CTRL + , (COMMA)
Looks like it was fixed since I last checked. Thanks!
My mistake, I can reproduce it in dev build 200809081401. It's a race condition though, so depending upon which file/position the error is at I either see this error or not. Even when I can reproduce it it occurs about 50% of the time. Essentially here is what I see: 1) User hits F11 to compile 2) User hits CTRL-. when the text "compiling X source files ..." shows up, *before* any error message shows up. 3) When the first error is found (and compilation is continuing), the caret moves to output window line associated with that error. For example, the caret moves to this line for me: "C:\Users\Gili\Documents\blueeye\trunk\desktopbeautifier\Client\java\source\desktopbeautifier\client\Main.java:71: cannot find symbol" 4) Normally, if you wait until compilation finishes and hit CTRL-. the caret will move to the line described in step 3, but the entire line will be highlighted *and* the editor will jump to the appropriate line/file. In the case of step 3, the line isn't highlighted and the editor position does not change. 5) Once compilation finishes, the user hits CTRL-. a second time. The caret now jumps to the second error listed in the output window, it is highlighted and the editor jumps to the correct position. In short here is what I am expecting: 1) Either the editor refuses to accept CTRL-. input until the compilation completes (it should beep on error or something), or... 2) If it accepts CTRL-. in mid-compilation it should highlight the line in the output window and jump to the correct editor window even on the first error.
d66ef1640f63
Integrated into 'main-golden', will be available in build *200810270201* on http://bits.netbeans.org/dev/nightly/ (upload may still be in progress) Changeset: http://hg.netbeans.org/main/rev/d66ef1640f63 User: Tomas Holy <t_h@netbeans.org> Log: #76071: Navigate | Next Error skips first error
The behaviour is still the same as gtzabari described. Pressing ctrl-. while compiling and before first error message is shown, does accept this shortcut and places carret to position of first error in output window, but does not highlight it, nor does it change view in editor. Issue cannot be market as verified. On the other hand, I would lower priority of this issue, I don`t find it to be too annoying (although it would be nice, if after compilation it jumps to the first compilation error, even without any user action, but that is not matter of this issue). Product Version: NetBeans IDE Dev (Build 200811181401) Java: 1.6.0_10; Java HotSpot(TM) Client VM 11.0-b15 System: Linux version 2.6.24-21-generic running on i386; UTF-8; en_US (nb)
You are mixing 2 things together. Ctrl+. before an error is printed does nothing. When an error hyperlink is printed to OW stops auto scrolling and place caret on error (without selecting or following link). Once you press Ctrl+. and there is hyperlink to follow the hyperlink is selected and navigation to file is fired. The issue reported was that first Ctrl+. went to second error not the first one. That was fixed.
ok, this works. marking as verified