Bugzilla – Full Text Bug Listing
| Summary: | initial search treats escaped chars different than subsequent line search | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Grant Gayed <grant_gayed> |
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | ||
| Version: | 5.0 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
| Whiteboard: | |||
Closing as part of a mass clean up of inactive bugs. Please reopen if this problem still occurs or is relevant to you. For more details see: https://dev.eclipse.org/mhonarc/lists/orion-dev/msg03444.html |
- open the Search page - search for: can't (not case sensitive, not a regular expression) - it returns a few matches, one of which (strings.js) shows "(No matches)", and no link is provided - the issue is that the string is escaped in the file: typesSelectionNomatch: 'Can\'t use \'%S\'.' - so the initial search finds it, but then a subsequent search (perhaps to determine its line number?) doesn't - these should be consistent so that it is either shown in the results with a line number+link or is not shown at all