Bug 293472 - Text search should not show regex pattern in job name when doing normal search
Summary: Text search should not show regex pattern in job name when doing normal search
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Search (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 minor (vote)
Target Milestone: ---   Edit
Assignee: Platform-Search-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-27 12:53 EDT by Dani Megert CLA
Modified: 2019-09-06 16:19 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Dani Megert CLA 2009-10-27 12:53:10 EDT 
I20091027-0100.

Text search should not show regex pattern in job name when doing normal search. It should use FileSearchQuery.getSearchString() instead of regex matcher's pattern.
Comment 1 Ludovic Aelbrecht CLA 2009-10-28 07:14:32 EDT 
Now that I think about it, it occurs to me that this is maybe more a feature than it is a bug. It's a relatively good way to clearly show what it's actually searching for...

My concern in bug 293449 was more with the time the search takes than with the name of the job. Now you've clarified it indeed interprets my search as a Java regex, I think showing the regex pattern isn't such a bad idea after all.

But that's up to you to decide. Either way, thanks for helping with this bug.
Comment 2 Dani Megert CLA 2009-10-28 07:21:59 EDT 
It should still show the pattern but the one that the user entered and not the regex pattern we use behind the scenes.
Comment 3 Eclipse Webmaster CLA 2019-09-06 16:19:26 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.