Bug 2821 - Text Search dialog should have a "Whole Word" check box. (1GJWI1I)
Summary: Text Search dialog should have a "Whole Word" check box. (1GJWI1I)
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Search (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: 3.0   Edit
Assignee: Platform-Search-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 19413 (view as bug list)
Depends on:
Blocks:
 
Reported: 2001-10-10 22:44 EDT by Kevin Haaland CLA
Modified: 2003-09-17 10:54 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kevin Haaland CLA 2001-10-10 22:44:12 EDT
Text Search dialog should have a "Whole Word" check box like the
	find replace dialog.

NOTES:
Comment 1 DJ Houghton CLA 2001-10-29 19:19:07 EST
PRODUCT VERSION:
	Build 135

Comment 2 Erich Gamma CLA 2002-01-25 04:26:50 EST
Agreed, that this would be useful. 

Search is is using the StringMatcher and it should provide this option. It 
currently only supports ignoreCase and ignoreWildcards. 

Once the string matcher supports this, it is trival to surface this in text 
search.

Nick, what is your opinion on adding this support to StringMatcher.
Comment 3 Nick Edgar CLA 2002-01-25 10:39:41 EST
StringMatcher should be taken out and shot <g>, but we can't do this until 
we're on JDK 1.4.  For now it's the right place to make this change.
If search wants to add it to their copy of StringMatcher, we can apply it to 
the others.  
Comment 4 Erich Gamma CLA 2002-05-04 19:42:57 EDT
we do not have the cycles to do StringMatcher tweaking, so we are also waiting 
for 1.4.
Comment 5 Dani Megert CLA 2003-04-10 13:21:43 EDT
reopen to close
Comment 6 Dani Megert CLA 2003-04-10 13:22:13 EDT
.
Comment 7 Dani Megert CLA 2003-04-10 13:22:24 EDT
there's now regEx support (use \bWORD\b)
Comment 8 Dani Megert CLA 2003-04-14 09:41:12 EDT
Had to revert the changes in Search plug-in until 1.4 is available on all
platforms. From the eclipse-dev mailing list:

>Please continue to use only J2SE 1.3 APIs in the main Eclipse development 
>stream.
>
>As indicated in the draft 2.2 plan, Eclipse mainline development will be 
>based on the current version of J2SE, namely 1.4. However, for some of the 
>operating environments we still need to identify suitable reference J2SE 
>1.4 implementations to use for development and testing. We won't make the 
>leap until we've completed these investigations. Please refrain from using 
>J2SE 1.4-specific APIs in this stream.

Comment 9 Dani Megert CLA 2003-04-14 09:42:47 EDT
*** Bug 19413 has been marked as a duplicate of this bug. ***
Comment 10 Dani Megert CLA 2003-04-14 09:46:35 EDT
The backed out code is tagged with "dm_RegEx_Support"
Comment 11 Archimedes Trajano CLA 2003-05-18 18:11:10 EDT
Can we utilize the Regular Expression library provided by Apache? 
http://jakarta.apache.org/regexp/index.html

Also if we do enable regular expressions in the searches, perhaps a button 
should be provided (if one is not there yet) that would bring up a help or 
cheat sheet for regular expressions and providing some common examples 
of "Whole word" matching.
Comment 12 Dani Megert CLA 2003-05-19 03:27:59 EDT
>Can we utilize the Regular Expression library provided by Apache? 
Since 3.0 will be 1.4 based we will use the standard RegEx package which covers
the needs for this and other regex related PRs. As you can see in comment 7 the
code which does whole word searching is already in the repository but is on hold
until the 3.0 stream sits on 1.4.x.

>Also if we do enable regular expressions in the searches, perhaps a button 
>should be provided (if one is not there yet) that would bring up a help or 
>cheat sheet for regular expressions and providing some common examples 
>of "Whole word" matching.
This information will be available via F1/Help.
Comment 13 Dani Megert CLA 2003-09-17 10:54:56 EDT
Available since I20030916.

The Regex Search feature request is not closed yet because we look into adding
content assist like support for regular expressions.