Bug 46481 - [EditorMgmt] history: Better File history
Summary: [EditorMgmt] history: Better File history
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-11-12 10:12 EST by Thorsten van Ellen CLA
Modified: 2019-09-06 15:37 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 Thorsten van Ellen CLA 2003-11-12 10:12:16 EST 
Hi!

Often I search occurrences of something, find several files, e.g. 50.
I open them and the last 4 of them are in the file history.
I close 20 of them again and the last 4 in the file history have not changed.
But I have closed the last file to early and want to reopen it,
but is not in the file history!!

It should not remember the files that have been OPENED at last,
but it should remember the files that have been CLOSED at last.

The File history (at the bottom of the file menu) 
seems to be able to remember only 4 filenames!
This should be configurable for at least 10 filenames!

best regards

Thorsten van Ellen
Comment 1 Thorsten van Ellen CLA 2005-02-03 15:23:24 EST 
at least partly fixed: 15 filenames possible in 3.0.1
Comment 2 Michael Van Meekeren CLA 2006-04-21 13:19:15 EDT 
Moving Dougs bugs
Comment 3 Susan McCourt CLA 2009-07-09 19:03:30 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Boris Bokowski CLA 2009-11-17 13:03:25 EST 
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 5 Eclipse Webmaster CLA 2019-09-06 15:37: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.