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

PowerShell Interactive Console Keeps Defaulting to White Text #46397

Closed
ghost opened this issue Mar 23, 2018 · 4 comments
Closed

PowerShell Interactive Console Keeps Defaulting to White Text #46397

ghost opened this issue Mar 23, 2018 · 4 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label

Comments

@ghost
Copy link

ghost commented Mar 23, 2018

Issue Type: Bug

I use PowerShell Language Mode in VS Code. That's all I want it for. I want the terminal to emulate the default Windows PowerShell console exactly - every time I launch VS Code. I have it configured to do it. I had only a single profile - 1 - powershell. And every time I launched VS Code, it opened to 1 - powershell.

This issue started immediately after the most recent update. Every time I launch VS Code, it now opens the terminal to PowerShell Integrated Console which uses a white-only typing scheme.

I want to be able to launch Visual Studio Code and have it open to the PowerShell terminal and have that PowerShell use the default console color scheme as-you-type. Meaning different colors for text dependent upon whether they are cmdlets, parameters, variables, etc.

For whatever reason(s), with the PowerShell extension installed, the PowerShell Language Mode selected, the terminal was opening to 1 - powershell which uses the same color scheme as you type as the default PowerShell console, but now it launches, opens to 1, then quickly switches to 2 - PowerShell Integrated Console - which uses only a white typing scheme.

It is really annoying because I am vision-impaired and the white-only lettering scheme of PowerShell Integrated Console just is not helpful. I have tried to figure out how to make it stop, searched online for answers, asked on PowerShell.org, etc but can find no answer.

VS Code version: Code 1.21.1 (79b44aa, 2018-03-14T14:46:47.128Z)
OS version: Windows_NT x64 10.0.16299

System Info
Item Value
CPUs Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz (8 x 2594)
Memory (System) 11.92GB (8.92GB free)
Process Argv C:\Program Files\Microsoft VS Code\Code.exe
Screen Reader no
VM 0%
Extensions (2)
Extension Author (truncated) Version
PowerShell ms- 1.6.0
vscode-icons rob 7.22.0
Reproduces only with extensions
@vscodebot
Copy link

vscodebot bot commented Mar 23, 2018

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Mar 23, 2018
@yume-chan
Copy link
Contributor

yume-chan commented Mar 23, 2018

Relates with PowerShell/vscode-powershell#535, I hope it will be resolved soon.

Before that, you can always switch back to your normal PowerShell console by selecting it from the dropdown menu above the console.

If you don't need the debugging functionality of PowerShell extension, you actually don't need the "PowerShell Integrated Console" thing, you can stop it from automatically popping up by setting powershell.integratedConsole.showOnStartup configuration to false.

@ghost
Copy link
Author

ghost commented Mar 23, 2018

The powershell.integratedConsole.showOnStartup configuration to false is not working. I already tried. PowerShell Integrated Console keeps loading with the above setting set to false.

Like I stated in my original report, this all started after this most recent update.

Time to uninstall Visual Studio Code.

@Tyriar
Copy link
Member

Tyriar commented Mar 23, 2018

I'll close this as a duplicate of #45693 and PowerShell/vscode-powershell#535

@Tyriar Tyriar closed this as completed Mar 23, 2018
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Mar 23, 2018
@vscodebot vscodebot bot locked and limited conversation to collaborators May 7, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label
Projects
None yet
Development

No branches or pull requests

2 participants