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 210455

Summary: Editor believes searching is usually followed by commenting out code
Product: editor Reporter: tbrunhoff <tbrunhoff>
Component: Hints & AnnotationsAssignee: Jan Lahoda <jlahoda>
Status: RESOLVED DUPLICATE    
Severity: normal CC: issues
Priority: P3    
Version: 7.2   
Hardware: PC   
OS: Linux   
Issue Type: DEFECT Exception Reporter:
Attachments: screenshot of lightbulb following search

Description tbrunhoff 2012-03-30 16:23:47 UTC
Created attachment 117566 [details]
screenshot of lightbulb following search

Whenever I search for something, the editor places a light bulb in the left margin so that I can easily add an editor-fold comment. When writing code, I can easily ignore this. However, when debugging, I most often search for variables/methods/etc in order to place a breakpoint.... and its not possible to set a breakpoint on any line that already has a light bulb in it. See attached screenshot.

You can work around this by clicking on another line first or hitting the hot key for setting a breakpoint, but this seems pretty irritating, because the editor is suggesting that this is something I always want to do when I search, and this is never something I do.

I think there are a couple of very good solutions that preserve this feature for its fans:
- In java, there are usually multiple options that pop up with alt-enter. Perhaps this should include an option for setting a breakpoint.
- Better, IMO, would be to allow the user to click in the column but provide a way that a breakpoint can still be set.
- Even better, IMO, is a UI option for turning off this feature.
Comment 1 Alexander Simon 2012-03-30 17:18:02 UTC
The same for java debugging.
Comment 2 tbrunhoff 2012-03-30 17:34:41 UTC
I note that, while debugging, the light-bulb does not show up for every search target. Stop debugging and the light bulbs show up again.
Comment 3 Jan Lahoda 2012-04-11 06:09:38 UTC

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