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

Keybinding to focus next terminal does not update terminal dropdown list #59876

Closed
carlocardella opened this issue Oct 3, 2018 · 14 comments
Closed
Assignees
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release terminal Integrated terminal issues verified Verification succeeded

Comments

@carlocardella
Copy link
Member

  • VSCode Version:
Version: 1.28.0-insider (user setup)
Commit: 85d970acdee48f6dcecf909a0faeb3c6882217a9
Date: 2018-10-02T22:27:52.997Z
Electron: 2.0.9
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
  • OS Version: Windows 10 Pro, 1803

I have added a keybinding to show the precious/next terminal when terminal has focus:

    {
        "key": "ctrl+tab",
        "command": "workbench.action.terminal.focusNext",
        "when": "terminalFocus"
    },
    {
        "key": "ctrl+shift+tab",
        "command": "workbench.action.terminal.focusPrevious",
        "when": "terminalFocus"
    },

The keybinding works as expected, the next or precious terminal is displayed but the dropdown with the list of open terminals is not updated accordingly, so it can be confusing to figure out which terminal is actually selected

powershell terminal
image

git bash, but the dropdown still shows the previous powershell terminal
image

If I use the dropdown to switch terminal then everything works as expected: the problem is with the keybinding

Does this issue occur when all extensions are disabled?: Yes

@vscodebot vscodebot bot added the terminal Integrated terminal issues label Oct 3, 2018
@martellaj
Copy link
Member

This isn't a new bug. It's a minor one that I haven't bothered creating an issue for, but finally decided to do it and found this. It's definitely been happening (on Insiders) for at least a week (possibly longer).

@Tyriar
Copy link
Member

Tyriar commented Oct 3, 2018

This only appears to happen on Windows, weird 😕 /cc @cleidigh

@Tyriar
Copy link
Member

Tyriar commented Oct 3, 2018

It also happens when running the command

@Tyriar Tyriar added the bug Issue identified by VS Code Team member as probable bug label Oct 5, 2018
@Tyriar
Copy link
Member

Tyriar commented Oct 6, 2018

This was introduced by abee50e

@Tyriar Tyriar added the candidate Issue identified as probable candidate for fixing in the next release label Oct 6, 2018
@Tyriar Tyriar added this to the September Recovery 2018 milestone Oct 6, 2018
@Tyriar Tyriar closed this as completed in 1e299b6 Oct 6, 2018
@Tyriar Tyriar reopened this Oct 6, 2018
@Tyriar
Copy link
Member

Tyriar commented Oct 6, 2018

Fixed in master, keeping open to pull into release/1.28

@cleidigh
Copy link
Contributor

cleidigh commented Oct 6, 2018

@Tyriar
Thanks.
I think with all your new features of terminal I have to add some more tests for the select box role :-(

@martellaj
Copy link
Member

Looks like it's resolved in today's Insiders build! 🎉

@carlocardella
Copy link
Member Author

Yes, it's resolved, thanks 👍

@Guema
Copy link

Guema commented Oct 9, 2018

Using AutoLaunch ext and got the same problem without using any shortcut. since last release only (1.28).

AutoLaunched task is displayed in terminal, but dropdown controls keeps bad state

Related ?

@Tyriar
Copy link
Member

Tyriar commented Oct 10, 2018

Merged into release/1.28 with #60545

@ddrrqq
Copy link

ddrrqq commented Oct 11, 2018

Good job! I use the Windows 10 1511 version, and I liked to use cmd.
I usually use tsc & web server in tasks.json, sometimes I switch them to view bugs infomation and use git or others, and it not work.
At first, I thought it was my cmd that caused this problem.
I tried a lot of ways to reset cmd settings. 😂

@1020431880
Copy link

嗨,程序猿们

@namnguyen6595
Copy link

i can't install 'pylint' via pip install. And this is my trouble
screenshot 13

@Tyriar
Copy link
Member

Tyriar commented Oct 15, 2018

@0888946595 report that against the python extension https://github.com/Microsoft/vscode-python

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 24, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue identified by VS Code Team member as probable bug candidate Issue identified as probable candidate for fixing in the next release terminal Integrated terminal issues verified Verification succeeded
Projects
None yet
Development

No branches or pull requests

9 participants