| Summary: | [client] extend URL hash to allow highlighting of a token within a line | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Susan McCourt <susan> |
| Component: | Client | Assignee: | Project Inbox <orion.client-inbox> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | libingw, mamacdon, Silenio_Quarti, simon_kaegi |
| Version: | 0.2 | Keywords: | polish |
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 358769 | ||
| Bug Blocks: | |||
|
Description
Susan McCourt
(In reply to comment #0) > > So we should probably support > highlight=foo > - with no other params, just highlight the first found (as if a ctrl-f were > done on that token) > - if a line number is also passed, the match is looked for in the line (the > outliner case) > - if a char position (or range) is passed, the match is looked for using the > range. I'd like to get the first case "highlight=foo" working for the June release. As it is now, when you use global search and click on a link, you are unhelpfully placed at the beginning of the file and have to go Ctrl-F yourself. ;-) Update: we now know the line number of a search hit, so we can now navigate directly to a line from global search. So the biggest pain point in not fixing this bug is now gone. The issue is now one of polish. Both the outliner and the global search results can position you to the correct line, but they do not highlight the token. Reassigning to inbox. I had this assigned to me so I could fix the "search results don't take you to the right line" problem. The remaining work would be nice but it not as important. Adding a dependency to bug 358769. I think it would make sense to add the "find next occurrence of token" support to the URL in general way (as a command/parameter combination) than in inventing something in particular. *** Bug 362717 has been marked as a duplicate of this bug. *** (In reply to comment #5) > *** Bug 362717 has been marked as a duplicate of this bug. *** I believe the "find next occurrence of token" will trigger the find&replace UI in editor, with your new command framework. But please correct me if otherwise. 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 |