Text search/replace support

[GoogleCodeExporter]

I'm thinking text search/replace support should be added before we do a 0.4
tag.  Implementation ideas are welcome.

Original issue reported on code.google.com by jpsut...@gmail.com on 29 Feb 2008 at 2:46

[GoogleCodeExporter]

I just found that there are APIs for these actions built into the QsciScintilla
library, so we should obviously use those. :)

Original comment by jpsut...@gmail.com on 9 Mar 2008 at 7:56

[GoogleCodeExporter]

I'm starting work on this now. :)

Original comment by jpsut...@gmail.com on 15 Mar 2008 at 3:13

• Changed state: Started

[GoogleCodeExporter]

I'm satisfied enough with simple find (sans replace) support to go ahead and 
tag the
0.4 release, but I'm leaving this issue open until we implement replace support.

Original comment by jpsut...@gmail.com on 19 Mar 2008 at 2:49

• Removed labels: Milestone-Release0.4

[GoogleCodeExporter]

Added Find/Replace dialog in r156

Original comment by jpsut...@gmail.com on 24 Aug 2008 at 4:23

[GoogleCodeExporter]

Added the Ctrl+f shortcut key for the find dialog and fixed some quirks in 
revision 
r164

Original comment by didoro...@gmail.com on 7 Jan 2010 at 2:47

[GoogleCodeExporter]

Replace functionality has been added (though it might not meet most people's 
preference) Also I re-worked the findreplace.ui file and eliminated the 
separate ui 
file for find.  The "From Cursor" and "Use Placeholders" checkboxes currently 
do not 
do anything.  From Cursor appears to be the default and "Use Placeholders" is 
not 
even hooked up.

FYI: Ctrl+H is the shortcut for the replace dialog.

see r166

Original comment by didoro...@gmail.com on 7 Jan 2010 at 7:18

[GoogleCodeExporter]

"Use Placeholders" sounds like it should be for some type of wildcard or regular
expression feature. I might see if I can get something like that hooked up over 
the
weekend.

Original comment by bfrobin...@gmail.com on 7 Jan 2010 at 6:25

[GoogleCodeExporter]

My idea behind that was to use it for regex group substitution.   

For example, in a regex like: (https?)://([^/]*)(/[^?]*)(?.*) 
one my have the following replace string: <a 
href="$1://www.somesite.com$3$4">$2</a>

where $1, $2, $3, $4 reference the groups (https?), ([^/]*), (/[^?]*), (?.*) 
respectively.

Granted this is sort of contrived but it should portray what is intended.  Many 
RegEx 
implemenations have tools to allow you to retrieve groups by number and it 
should be 
relatively trivial to accomplish.

Might be good to disable the option if the regex checkbox is not checked.

Original comment by didoro...@gmail.com on 7 Jan 2010 at 9:02

[GoogleCodeExporter]

Better yet, have the "Use Placeholders" option imply the Regex option (when you 
check 
the first, it automatically checks the second, and prevents it from being 
unchecked).

Original comment by jpsut...@gmail.com on 7 Jan 2010 at 9:13

[GoogleCodeExporter]

Apparently scintilla provides placeholder support: 
http://www.scintilla.org/ScintillaDoc.html#Searching

Look down till you see the list of escape characters.  The few of note are: 
'\(', 
'\)', and '\n'.

This is not the typical regex style perhaps we should make the search when 
regex is 
selected more complex and use a QRegEx.  According to 
http://www.scintilla.org/ScintillaDoc.html#AlternativeRegEx we could compile 
our own 
in if we custom compiled qscintilla. Not sure if we want to do that or not.

Original comment by didoro...@gmail.com on 8 Jan 2010 at 2:50