Bug 85632 - [EditorMgmt] Editor history is not kept correctly
Summary: [EditorMgmt] Editor history is not kept correctly
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-02-16 20:09 EST by Chris Laffra CLA
Modified: 2019-09-06 16:15 EDT (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Chris Laffra CLA 2005-02-16 20:09:13 EST
On Eclipse Build id: I20050214-0927.

I opened two Java files. I switched between the two. Pressing Alt+Left moves 
me back between the two editors as expected.

Then, I go to Package Explorer. I rename the file I am currently _not_ 
editing. Then, when I press Alt+Left the editor wants to warp back to the file 
that no longer exists and brings up an error dialog.

Seems like editor history wants to be a workspace listener?
Comment 1 Victor Toni CLA 2005-03-01 19:58:31 EST
The same happens if the not active file has been deleted.
The history should delete this entry too.
Comment 2 Dani Megert CLA 2005-03-08 09:48:34 EST
The history is managed by Platform UI.
Comment 3 Michael Van Meekeren CLA 2006-04-21 13:19:10 EDT
Moving Dougs bugs
Comment 4 Susan McCourt CLA 2009-07-09 19:06:48 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 5 Boris Bokowski CLA 2009-11-17 13:02:36 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:15:21 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.