Bugzilla – Full Text Bug Listing
| Summary: | [search results] navigating to other files with search hits from the editor | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> | ||||
| Component: | Client | Assignee: | libing wang <libingw> | ||||
| Status: | RESOLVED WONTFIX | QA Contact: | |||||
| Severity: | enhancement | ||||||
| Priority: | P3 | CC: | john.arthorne, libingw, Mike_Wilson | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
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 |
Created attachment 203930 [details] screenshot of how bugzilla does it (or just look at the top of this bugzilla page!) I was noticing today how bugzilla includes search results list context when you open a bug. In Orion-speak, that would mean that opening an editor from the search results page would remember some of the context of the original search, so that you could navigate across the search results from the editor. Note that I don't just mean navigate the hits within that file, I mean navigate to the next file that contains a hit. In bugzilla this makes sense because you pretty much always find a bug by searching for it. Not sure we would want to preserve real estate on the editor to show what search results found it, but I thought it was an interesting thing to think about, because then you would have the eclipse global/search replace workflow, where you want to visit each hit and do something. Attaching screen shot.