I believe this should be the default behavior because it aligns with user intent: no matter where I'm at in the editor, if I hit the hotkey it should bring me to the respective panel. If I'm already there I probably want to toggle it.

I am ok changing this, the sidebar behaves the same (focus in when not focussed and invoking the keybinding). As long as we provide a way to configure the old behaviour.

Should be changed, yes. I'm using almost exclusively using workbench.action.focusPanel as soon as the terminal is active because I can't stand the do-2-things-at-once-behaviour of workbench.action.terminal.focus.

Consistency with the sidebar would be a big plus 👍

I am fine with changing this to behave like the sidebar. Especially if the users seem to prefer this. They can always use cmd + J to toggle

This was brought up already before - #7540

+1 for the change.

I cannot emphasize how many times I have had to invoke the shortcut twice solely to regain focus on the terminal. Definitely a usability flaw

@isidorn to be clear I'm proposing a conditional focus though so it would not be consistent with the sidebar, just a little more like the sidebar's behavior.

Personally, i would just like to switch cursor between terminal and editor without hiding terminal. This setting works for me.
'{
"key": "ctrl+`",
"command": "workbench.action.terminal.focus",
"when": "!terminalFocus"
},
{
"key": "ctrl+`",
"command": "workbench.action.focusActiveEditorGroup",
"when": "terminalFocus"
}'

This keybinding works in v1.15.0 ctrl+Alt+'

However, it's one of the most awkward key combinations ever!

@dbaeumer @isidorn @sandy081 this is currently blocked on when context clauses for output, problems and tasks which I don't think exist currently https://code.visualstudio.com/docs/getstarted/keybindings#_when-clause-contexts

I'd be happy to make the keybinding changes after the contexts are implemented.

@bpasero I'm not suggesting adding another command, rather adding new default keybindings:

{
  "key": "ctrl+`",
  "command": "workbench.action.terminal.focus",
  "when": "!terminalFocus"
},
{
  "key": "shift+ctrl+m",
  "command": "workbench.action.problems.focus",
  "when": "!problemsFocus"
},
...

When the panel is open and focused: It should focus the editor (so you can jump in and out)

This doesn't really solve the problem though imo, I use ctrl/cmd+1 when I want to switch back to the editor personally. The above keybindings just makes it nicer to work with the terminal such that you don't need to trigger toggle terminal twice if it's already visible. I often recommend people use this setup for toggle terminal and I've only heard positive feedback.

@Tyriar I still dislike the fact that viewlets behave differently from panels

@Tyriar I have a change ready in c7b740f that would change every panel toggle action to behave as outlined in #19400 (comment). I do not think we can just fix this via changing our default keybindings, because what about people that have changed the keybindings manually?

@bpasero looks ok, one thing to keep in mind is that doing it this way makes you unable to hide the panels via the command palette. You can still use "toggle panel", but "toggle terminal" will actually focus the terminal since the command palette was focused.

Good point, I suggest we talk about this in the UX call.

The behaviour of the commands for toggling panels has changed as outlined in #19400 (comment). To get back the previous behaviour, simply configure a keybinding to close the panel when the related panel is active, e.g. for output:

{
	"key": "cmd+shift+u",
	"command": "workbench.action.closePanel",
	"when": "activePanel==workbench.panel.output"
}

The list of panel identifiers is:

• workbench.panel.terminal
• workbench.panel.markers
• workbench.panel.output
• workbench.panel.repl

Verification: see #19400 (comment)

@bpasero I think you took @Tyriar comment a bit too literarly. I verified it works great, however there is one corner case which is a regression, thus reopening

1. View > terminal -> terminal gets nicely opened
2. View > output -> panel gets closed. Instead the output should be shown

Wow, not sure how I did not test that. Fixed, thanks!

I found the link to this issue in release notes for the 1.28.2 release and I like the way how ctrl + ` behaves now. I also was annoyed by the fact that I have to type terminal shortcut twice if I want to move back to the terminal.

But what shortcut can I use to move back from the terminal to an editor? I mean, I don't want to close a terminal panel. I want to leave it open and switch focus to an editor. A use case for this would be the following: I will write in the editor a code that depends on the result of a teminal command that I just run. So I want to move focus from terminal to an editor and leave terminal open.

@plagov just add a custom shortcut to this command

@plagov try Ctrl+P Esc