Bug 77271 - [EditorMgmt] tabs: Offer 'close all but most recent' editors in editor tab
Summary: [EditorMgmt] tabs: Offer 'close all but most recent' editors in editor tab
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-10-29 07:25 EDT by Philipe Mulet CLA
Modified: 2019-09-06 16:14 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Philipe Mulet CLA 2004-10-29 07:25:48 EDT
Build 3.1M2

There are several 'close' action variations available by right click in '>>'
editor tab area. One of the missing one would be to close all but the most
recently used ones (number depending on preference: 'number of opened editors
before closing').

This way, when not using the 'close editors automatically' mode, I would still
be able to flush obsolete ones at some checkpoint in a quick fashion.
Comment 1 Gregor Rosenauer CLA 2005-09-14 07:37:23 EDT
I'd also agree this functionality.
A simple solution would be an option to close all *invisible* editors, which are
hidden in the ">>"-dropdown-menu.
The hidden items are most likely the ones I am not working at the moment and
want to get rid of (for freeing up some resources - Eclipse is still a
resource-intensive app).
Comment 2 Michael Van Meekeren CLA 2006-04-21 13:19:37 EDT
Moving Dougs bugs
Comment 3 Susan McCourt CLA 2009-07-09 19:06:20 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 4 Boris Bokowski CLA 2009-11-17 13:03:10 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 5 Eclipse Webmaster CLA 2019-09-06 16:14:51 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.