-
Notifications
You must be signed in to change notification settings - Fork 29.5k
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
Comments
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! |
Yes, set |
Ah, great thanks! ☺ Also for quickest than quicker reply 😏 |
Please never remove the "old" way. I tried going back to tabs.... it was painful. |
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. |
|
Great, thanks! |
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 groupworkbench.action.clearEditorHistory
: clear navigation history and list of recently closed editorsworkbench.action.closeEditorsInGroup
: close all editors of a groupworkbench.action.closeEditorsInOtherGroups
: close editors in other groupsworkbench.action.closeEditorsToTheLeft
: close editors to the left of the active oneworkbench.action.closeEditorsToTheRight
: close editors to the right of the active oneworkbench.action.openLastEditorInGroup
: open last editor in groupworkbench.action.openEditorAtIndex[1-9]
: open editor at indexworkbench.action.openNextRecentlyUsedEditorInGroup
: navigate forwards in MRU list of editors of a groupworkbench.action.openPreviousRecentlyUsedEditorInGroup
: navigate backwards in MRU list of editors of a groupSettings 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: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
Windows/Linux
The text was updated successfully, but these errors were encountered: