Bug 107928 - [Markers] need possibility to step to bookmarks with keyboard keys
Summary: [Markers] need possibility to step to bookmarks with keyboard keys
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: IDE (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-08-24 15:58 EDT by Igor Galchevsky CLA
Modified: 2019-09-06 16:17 EDT (History)
0 users

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 Igor Galchevsky CLA 2005-08-24 15:58:22 EDT 
Eclipse provides possibility to add bookmarks with keyboard keys but i can't
find any possibility to goto added bookmark using keys.
Comment 1 Olivier Thomann CLA 2005-08-24 16:21:13 EDT 
Move to Platform/UI
Comment 2 Eugene Lucash CLA 2005-08-25 13:40:46 EDT 
I think there must be a way in Eclipse to cycle thought series of bookmarks with
some enough easy keyboard shotcut. Also it would be great to have some mechanism
to quickly bind different edit locations to concrete keyboard shortcuts.
For example I bookmark an edit location with ctrl+shift+F1, and to go back to it
I might use ctrl+F1. I can bind ctrl+F2, ctrl+F3 and so on.. So jumps are easy
and very controlled
Comment 3 Tod Creasey CLA 2006-04-07 14:51:06 EDT 
There are no plans to work on this feature
Comment 4 Igor Galchevsky CLA 2006-04-08 06:19:32 EDT 
(In reply to comment #3)
> There are no plans to work on this feature
But why? It is very usable feature, most IDE have it!
Comment 5 Tod Creasey CLA 2006-04-10 07:56:06 EDT 
Reopening as requested
Comment 6 Susan McCourt CLA 2009-07-15 12:16:32 EDT 
"As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009"
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:17:24 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.