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 221304 - automatic closing square bracket doesnt get overwritten with the typed one
Summary: automatic closing square bracket doesnt get overwritten with the typed one
Status: RESOLVED FIXED
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 7.2.1
Hardware: Macintosh Mac OS X
: P3 normal (vote)
Assignee: Milutin Kristofic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-11-02 02:17 UTC by yeswoman
Modified: 2012-11-07 22:57 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
IDE log (32.98 KB, text/plain)
2012-11-02 02:17 UTC, yeswoman 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description yeswoman 2012-11-02 02:17:36 UTC 
Product Version = NetBeans IDE 7.2.1 (Build 201210100934)
Operating System = Mac OS X version 10.8.2 running on x86_64
Java; VM; Vendor = 1.6.0_37
Runtime = Java HotSpot(TM) 64-Bit Server VM 20.12-b01-434

when opening a square bracket [ it automatically creates a closing square bracket ]
but after writing something inside those brackets, I type the closing square bracket on the keyboard and netbeans doesn't overwrite the automatically created closing bracket with the closing bracket that I typed. it should overwrite it so that i can continue coding comfortably.
thank you!
Comment 1 yeswoman 2012-11-02 02:17:40 UTC 
Created attachment 126965 [details]
IDE log
Comment 2 Milutin Kristofic 2012-11-06 17:14:58 UTC 
I cannot reproduce this.

I press [
I have [|] where | is caret
I press ]
I have []| 
I press [
I have [][|]
I press t
I have [][t|]
I press ]
I have [][t]|


Please show me your case in similar way.
Comment 3 yeswoman 2012-11-07 22:57:26 UTC 
nevermind. it is not behaving like this anymore. it's doing what it's supposed to do. it was probably the computer restart that fixed it.