Bug 63175 - [EditorMgmt] most recently closed file not showing up in recently used files
Summary: [EditorMgmt] most recently closed file not showing up in recently used files
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-20 05:59 EDT by Noel Grandin CLA
Modified: 2019-09-06 16:05 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Noel Grandin CLA 2004-05-20 05:59:38 EDT
Use Case:
I open Editor E1 and E2 in my environment. Then I proceed to open editors 
E3...E20. Then I close editors E3...E20.
Then I close editor E2.
At this point I realize that I actually wanted to carry on working on editor 
E2, but it's not in the File menu's list of recently used editors anymore.

This is fairly common for me - I have a small set of files that I work on a 
lot, and then a number of other files I open briefly. If I accidentally close 
one of my "a lot" files, there is no way to get back to it quickly.

This appears to be a problem because my mental model of the recently used files 
list is "files I worked on most recently", but the code appears to using a FIFO 
and adding files to the FIFO at editor __open time__, leading to the scenario 
outlined above.

Proposed solution: At editor close time, add it to the FIFO again (obviously 
removing it if it is still in the FIFO). This should make recently closed 
editors "newer" in the FIFO and less likely to get bumped off.
Comment 1 Michael Van Meekeren CLA 2006-04-21 13:19:19 EDT
Moving Dougs bugs
Comment 2 Susan McCourt CLA 2009-07-09 19:04:57 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 3 Boris Bokowski CLA 2009-11-17 13:07:04 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Eclipse Webmaster CLA 2019-09-06 16:05:26 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.