Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stacks & Tabs: Added or changed commands #6605

Closed
bpasero opened this issue May 21, 2016 · 7 comments
Closed

Stacks & Tabs: Added or changed commands #6605

bpasero opened this issue May 21, 2016 · 7 comments
Assignees
Labels
workbench-tabs VS Code editor tab issues
Milestone

Comments

@bpasero
Copy link
Member

bpasero commented May 21, 2016

With the introduction of tabs and editor stacks to VS Code, we introduced many new commands and changed some existing ones. Due to the fact that the Working Files view is replaced by the Opened Editors view, some commands also got replaced by others. Below is a list of changed and new commands:

Changed Commands

  • workbench.action.focusFirstEditor => workbench.action.focusFirstEditorGroup
  • workbench.action.focusSecondEditor => workbench.action.focusSecondEditorGroup
  • workbench.action.focusThirdEditor => workbench.action.focusThirdEditorGroup
  • workbench.action.focusLeftEditor => workbench.action.focusPreviousGroup
  • workbench.action.focusRightEditor => workbench.action.focusNextGroup
  • workbench.action.moveActiveEditorLeft => workbench.action.moveActiveEditorGroupLeft
  • workbench.action.moveActiveEditorRight => workbench.action.moveActiveEditorGroupRight
  • workbench.action.openPreviousEditor => workbench.action.openPreviousEditorFromHistory
  • workbench.files.action.addToWorkingFiles => workbench.action.keepEditor
  • workbench.files.action.closeAllFiles => workbench.action.closeAllEditors
  • workbench.files.action.closeFile => workbench.action.closeActiveEditor
  • workbench.files.action.closeOtherFiles => workbench.action.closeOtherEditors
  • workbench.files.action.focusWorkingFiles => workbench.files.action.focusOpenEditorsView
  • workbench.files.action.openNextWorkingFile => workbench.action.nextEditor
  • workbench.files.action.openPreviousWorkingFile => workbench.action.previousEditor
  • workbench.files.action.reopenClosedFile => workbench.action.reopenClosedEditor
  • workbench.files.action.workingFilesPicker => workbench.action.showAllEditors
  • workbench.action.cycleEditor => workbench.action.navigateEditorGroups

New Commands

  • workbench.action.showEditorsInGroup: show all editors of a group
  • workbench.action.clearEditorHistory: clear navigation history and list of recently closed editors
  • workbench.action.closeEditorsInGroup: close all editors of a group
  • workbench.action.closeEditorsInOtherGroups: close editors in other groups
  • workbench.action.closeEditorsToTheLeft: close editors to the left of the active one
  • workbench.action.closeEditorsToTheRight: close editors to the right of the active one
  • workbench.action.openLastEditorInGroup: open last editor in group
  • workbench.action.openEditorAtIndex[1-9]: open editor at index
  • workbench.action.openNextRecentlyUsedEditorInGroup: navigate forwards in MRU list of editors of a group
  • workbench.action.openPreviousRecentlyUsedEditorInGroup: navigate backwards in MRU list of editors of a group

Settings for old non-stacks behaviour

If you want to configure VS Code to get some of the old behaviour back, see the following configurations.

Ctrl+Tab to navigate in entire editor history

You can change keybindings for Ctrl+Tab to show you a list of all opened editors from the history independent from the editors that are opened in a stack. Edit your keybindings and add the following:

{ "key": "ctrl+tab", "command": "workbench.action.openPreviousEditorFromHistory" },
{ "key": "ctrl+tab", "command": "workbench.action.quickOpenNavigateNext", "when": "inQuickOpen" },

Close an entire group instead of a single editor

If you liked the behaviour of VS Code closing an entire group when closing one editor, you can bind the following in your keybindings configuration:

Mac
{ "key": "cmd+w", "command": "workbench.action.closeEditorsInGroup" }
Windows/Linux
{ "key": "ctrl+w", "command": "workbench.action.closeEditorsInGroup" }
@bpasero bpasero added workbench workbench-tabs VS Code editor tab issues labels May 21, 2016
@bpasero bpasero added this to the June 2016 milestone May 21, 2016
@bpasero bpasero self-assigned this May 21, 2016
@bpasero bpasero closed this as completed May 30, 2016
@bpasero bpasero changed the title Stacks: Document changed command ids and how to get old behaviour back Stacks: added or changed command ids Jun 9, 2016
@bpasero bpasero changed the title Stacks: added or changed command ids Stacks & Tabs: Added or changed commands Jun 19, 2016
This was referenced Jun 28, 2016
@cthedot
Copy link

cthedot commented Jul 9, 2016

Got so used to "Ctrl+Tab to navigate in entire editor history" I added the Keyboard Settings. But seems opening files this way does not add a new tab but replaces a tab? Any way to open a file in a new tab? Thanks!

@bpasero
Copy link
Member Author

bpasero commented Jul 9, 2016

Yes, set workbench.editor.enablePreviewFromQuickOpen: false in your settings.

@cthedot
Copy link

cthedot commented Jul 9, 2016

Ah, great thanks! ☺

Also for quickest than quicker reply 😏

@maritz
Copy link

maritz commented Jul 25, 2016

Please never remove the "old" way. I tried going back to tabs.... it was painful.

@varungupta85
Copy link

Is there a way to also remove the tab bar on the top? I have gotten used to the old behavior where there was not tab bar on the top and started to like it. Much less clutter.

@maritz
Copy link

maritz commented Aug 5, 2016

@varungupta85

"workbench.editor.showTabs": false

@varungupta85
Copy link

Great, thanks!

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
workbench-tabs VS Code editor tab issues
Projects
None yet
Development

No branches or pull requests

4 participants