Community
Participate
Working Groups
M4 testpass on I20031007 + plugin-export 20031008_1008 - do an Edit > Find/Replace with regular expressions - do something else - select a text range with regexp special characters in a text editor (e.g.: ".setText(") - press Ctrl+F -> the selected text is entered in the "Find:" field -> clicking "Find" will fail since the text is not a valid regular expression => I suggest unchecking "Regular expressions" when a text selection is taken over as search pattern
The dialog is shared between editors and switching would always reset. We could uncheck it the very first time the dialog gets opened with a selection. Kai?
Actually, my original request was not so clever. The right approach is to *escape* the taken-up selection if regex search is enabled (insert '\' before special characters). This should be done for 'Find Next' (Ctrl+K), 'Find Previous', and the 'Find/Replace...' (Ctrl+F) dialog. Another failing case: if regex search is enabled in the Find/Replace dialog, selecting something like "update(true)" and pressing Ctrl+K does not find the next "update(true)" since the parenthesis are interpreted as regex capturing group. Changing title from 'Find/Replace dialog should uncheck "Regular expressions" when taking text selection'.
*** Bug 129764 has been marked as a duplicate of this bug. ***
*** Bug 44799 has been marked as a duplicate of this bug. ***
Created attachment 71464 [details] Fix The fix implements comment 2. It contains this workaround for bug 192837 in two places (workaround can be removed when bug 192837 is fixed): if (fullSelection == null) // workaround for bug 192837 fullSelection= ""; //$NON-NLS-1$
Thanks Markus. Committed to HEAD. Available in builds > N20070715-0010.