Bug 312158 - [EditorMgmt] There is no keyboard support to split and unsplit editor screens.
Summary: [EditorMgmt] There is no keyboard support to split and unsplit editor screens.
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.6   Edit
Hardware: All All
: P3 enhancement with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-08 09:43 EDT by Pedro Rolo CLA
Modified: 2019-09-06 16:09 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 Pedro Rolo CLA 2010-05-08 09:43:39 EDT
Build Identifier: 

There is no keyboard support to split and unsplit editor screens and to alternate between selected editor frames.

Reproducible: Always
Comment 1 Remy Suen CLA 2010-05-08 12:34:52 EDT
(In reply to comment #0)
> There is no keyboard support to split and unsplit editor screens and to
> alternate between selected editor frames.

You mean a keybinding to replace the need to drag an editor by hand and create a new editor stack, yes?
Comment 2 Pedro Rolo CLA 2010-05-09 09:47:45 EDT
Yes, I mean that. There should be keyboard shortcuts to split horizontally, split vertically, unsplit, and change the selected "editor stack".

Examples can be seen in emacs, with the keyboard shortcuts C-0,C-1,C-2,C-3 and C-o.
Comment 3 Pedro Rolo CLA 2010-05-09 09:53:24 EDT
Addidtionaly, The control-click function could be parametrized to alternate the "editor stack" where it would open new files.

In this way, the caller's context could be kept on screen, providing a more holistic view of the code.

This would of course be an experimental feature. If you believe that it is an interesting suggestion say so, and I will create a new feature request.
Comment 4 Remy Suen CLA 2010-05-09 09:56:24 EDT
(In reply to comment #3)
> Addidtionaly, The control-click function could be parametrized to alternate the
> "editor stack" where it would open new files.
> 
> In this way, the caller's context could be kept on screen, providing a more
> holistic view of the code.

This sounds like every time a file is opened, you want it to open in the non active stack, is this correct? If yes, please open a separate enhancement request. If no, please open another one anyway because this bug is for the introduction of keybindings.
Comment 5 Pedro Rolo CLA 2010-05-09 10:10:32 EDT
I have created a new feature request for the "open new files in non-selected stack" feature.
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:09:49 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.