Version: 3.0.0a5 (using KDE 3.1.1) Compiler: gcc version 3.2.1 20021207 (Gentoo Linux 3.2.1-20021207) OS: Linux (i686) release 2.4.20-gentoo-r2 when editing source code and trying to replace something using a previously used regular expression, the regex matching option in the replace dialog has to be selected first and then the regex can be selected, otherwise the regex will not match. this bug is reproduceable in the latest cvs version to this date.
Just to verify before I'm reassigning: You are using the kate editorpart (called "Embedded Advanced Text Editor" in the settings) and are referring to the "local" replace (found through edit -> replace or CTRL+R), correct?
Subject: Re: replace feature requires to select regex matching for the search pattern before selecting the regex from the drop down box, otherwise it will not match Jens Dagerbo wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=61283 > > > > > ------- Additional Comments From jens.dagerbo@swipnet.se 2003-07-23 12:04 ------- > Just to verify before I'm reassigning: > > You are using the kate editorpart (called "Embedded Advanced Text Editor" in the > settings) and are referring to the "local" replace (found through edit -> replace or > CTRL+R), correct? Yes, that's right, I have only the kate editorpart installed. I have found an addition to my bug, the use selected text checkbox has the same bug as the regex checkbox. Replacing only works if the checkbox is checked *before* the search pattern and replacement text is entered, otherwise it will not replace anything because it does not find anything. (Or should I report another bug?)
Reassigning
that works flawless with kde cvs head, or ? could somebody recheck before I close this bug, anders ? jesse ?
No, I don't see it. I tried some combinations of regexp searches and normal ones. In all cases I was able to select the various options even though I had already entered the text in (or in some cases was provided for me automagically) and the options were applied accordingly to the search. Similarly, the 'Selected Text' seems to work too. I selected this option *after* I had entered in the search and replace fields (directly contrary to the report) and it worked. It even worked with a regexp search as well ;) Also tried the same set of tests in kdevelop just to check.
fine, than not only my impression is that this issue has been solved for 3.2, but no idea why it could have been ever there personally