Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 275541 - [navigation] Add history to Ctrl-Q
Summary: [navigation] Add history to Ctrl-Q
Status: RESOLVED DUPLICATE of bug 72773
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.4.2   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-05-09 14:01 EDT by Aaron Digulla CLA
Modified: 2009-05-11 11:54 EDT (History)
3 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Aaron Digulla CLA 2009-05-09 14:01:26 EDT
When you press Ctrl-Q, you return to the last place where you edited something. Pressing Ctrl-Q again doesn't do anything anymore.

Please change the feature so that pressing Ctrl-Q again returns you to the second last edit place, etc. This would allow to return to your original place after making a small modification in a different place.

Ctrl-Shift-Q should go forward in the history.
Comment 1 Remy Suen CLA 2009-05-09 14:14:12 EDT
Does Alt+Left and Alt+Right help?
Comment 2 Aaron Digulla CLA 2009-05-09 15:36:21 EDT
Going forward and backward through the history where I was (instead of where I changed something) doesn't help me for two reasons:

1. I remember places where I changed something better than places where I looked.

2. I haven't yet figured out how Eclipse builds the list of places which I can visit with Alt+Left/Right. When I use this function, I rarely end up where I think I was before. Instead, the places I see are somewhat random, often, I see places in the code where I haven't been for days (or so I think). This might be a bug or some malfunction in my brain but for me, Alt+Left/Right doesn't work well and I rarely use it.
Comment 3 Dani Megert CLA 2009-05-11 11:54:00 EDT

*** This bug has been marked as a duplicate of bug 72773 ***