Bug 64256 - [EditorMgmt] Enhancement to change/switch editor behavior
Summary: [EditorMgmt] Enhancement to change/switch editor behavior
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: PC Linux
: P3 enhancement with 2 votes (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-05-26 18:56 EDT by Dirk Bergstrom 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 Dirk Bergstrom CLA 2004-05-26 18:56:59 EDT
There are three separate ways to change the active editor.  They're similar, and
they have similar names, so it's very hard to figure out which does what based
on the name.  I do a lot of switching between editors, and I'd like to see the
functionality condensed and streamlined.

Here's the three methods:

"Open Editor Dropdown" - Shows a list of open editors, allows type-ahead-find
for editor name.  Hitting return dismisses the list.

"Next Editor" - Brings up a list of editors with the current editor on top, and
the most recently visited editors below that.  The previously visited editor is
highlighted.

"Switch to Editor" - Opens a very large dialog with a bunch of buttons that have
little to do with switching editors ("Select Clean Editors", etc.)

I use "Next Editor" most frequently, since I generally want to switch repeatedly
between two editors.  However, I find it frustrating that when the editor I want
isn't one of the recently used ones, I have to visually search the list, then
hold down the down arrow to get to it.

It would be great if the functionality of "Open Editor Dropdown" was combined
with that of "Next Editor", so that you got the dropdown, with the editors in
most-recently-used order, with the most recent one highlighted.  That way you
could either:
 - hit return to get to the editor you most likely want.
 - use the down arrow to get to the other recently used editors
 - start typing the name of another editor to quickly find it.

This would really speed up my work.

I've never used "Switch to Editor", and I can't see the value in it.  At the
very least it needs to be renamed; really it should either be removed, or
expanded into a "Manage Editors" dialog (like the Buffer List function in emacs).

Thanks.
Comment 1 Jerry Quinn CLA 2005-01-08 13:50:39 EST
Another issue is that there is a key binding to get to the Switch To Editor
dialog box (triggered by C-x C-b in emacs mode), but no way to get to the drop
down with a keybinding, which I would expect to be C-x b in emacs mode.  You can
only get to the drop down with the mouse, either through
Window->Navigation->Switch to Editor, or clicking on the little >> icon.

The fact that the menu option brings up a different dialog than the C-x C-b
binding is strange as well.

As the originator mentions, being able to type the name of the buffer is
important and the switch to editor dialog brought up by the keybinding doesn't
allow that, making it much less useful.
Comment 2 Michael Van Meekeren CLA 2006-04-21 13:19:14 EDT
Moving Dougs bugs
Comment 3 Ben Dodson CLA 2006-08-18 11:09:01 EDT
It seems like this was added, as C-x b works as expected. Thanks a ton :) One thing I would love to see to make it a bit more like it is in Emacs: it would be nice if the box would default to the last editor used, so that 'C-x b <enter>' would switch to the last editor. 
Comment 4 Ben Martin CLA 2007-12-22 19:51:05 EST
I would also love to see 'C-x b <enter>' work as mentioned in C#3. Its a binding that you can very quickly get used to using in emacs.
Comment 5 Susan McCourt CLA 2009-07-09 19:05:04 EDT
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 6 Boris Bokowski CLA 2009-11-17 13:04:57 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:15:59 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.