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.
Currently search and replace honors the case typed into the search dialog. For example, if I have the text: public void setCharProperty(char value) { char oldValue = this.charProperty; this.charProperty = value; support.firePropertyChange("charProperty", oldValue, value); } with a search text of char and a replace text of string, I end up with: public void setstringProperty(string value) { string oldValue = this.stringProperty; this.stringProperty = value; support.firePropertyChange("stringProperty", oldValue, value); } Which isn't really what I wanted. Instead I want the replaced text to end up in the same case as that of the text being replaced: public void setStringProperty(String value) { String oldValue = this.stringProperty; this.stringProperty = value; support.firePropertyChange("stringProperty", oldValue, value); } This makes it so much easier to search and replace text as you don't have to worry about the case. Emacs has been doing this for years.
> Which isn't really what I wanted. Instead I want the replaced text to end up in > the same case as that of the text being replaced: Strictly speaking, following your rule, the text after replacing would look like this: public void setStringProperty(string value) { string oldValue = this.stringProperty; this.stringProperty = value; support.firePropertyChange("stringProperty", oldValue, value); } It would be better than nothing, but the 'string' as a type of the method parameter and oldValue would still cause a compilation error. Anyway, I think I got your point and I agree that this should be improved. Thanks
*** This issue has been marked as a duplicate of 80732 ***