Terminal not getting activated in Insiders
See original GitHub issueActivation of environments is broken in VSC Insiders.
The configuration setting terminal.integrated.shell.<platform>
returns null in insiders.
See below:
- Operating System: Mac
- Works in Stable
- Does not work in Insiders
Version 1.34.0 (1.34.0)
Version 1.35.0-insider (1.35.0-insider) 2019-05-23T05:07:54.582Z
Issue Analytics
- State:
- Created 4 years ago
- Reactions:1
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Cannot open terminal after using the code-insiders command ...
I'm not saying that it doesn't work. The only problem I'm reporting when having shell integration enabled + oh-my-zsh is that the terminal...
Read more >Visual Studio (VS-code) code terminal is failing to launch
Now the terminal should open again. This is not a fix to get Powershell working in VS Code, just a guide to restore...
Read more >Terminal Shell Integration in Visual Studio Code
Visual Studio Code's embedded terminal can integrate with some shells to enhance the capabilities of the terminal.
Read more >Get started with the Windows Insider Program - Microsoft Learn
Follow the directions on your screen to choose the experience and channel you'd like to get Insider Preview builds through. (Not sure which ......
Read more >Player-activated terminal Definition | Law Insider
Define Player-activated terminal. means a device authorized by the lottery and operated by a player to function in an online, interactive mode with...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
I closed the vscode issue, please try fix this on your end before we go out with 1.35 stable (sometime next week). The proposal is to leverage
Terminal.name
when you’re sending something to a terminal you don’t own (see https://github.com/microsoft/vscode/issues/74233#issuecomment-497527337) and otherwise when the shell is null fill it in with your own default (like this).The reason the fix has to be on the side of extensions is because otherwise extensions will break when connected to remotes.
Proper fix proposal -> https://github.com/microsoft/vscode/issues/75091, it will still need extensions to adopt it though.