Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Insiders] Cannot change Terminal Name from "Powershell Integrated Console"

See original GitHub issue

Issue Type: Bug

You can use $host.ui.RawUI.WindowTitle to set the title on a normal terminal in latest vscode insiders. The powershell extension overrides this for the integrated terminal, there should be an option to support setting from the UI terminal. This will need to be careful to ignore the initial Powershell window setting, but allow everything from basically the profile onwards.

Extension version: 2020.6.1 VS Code version: Code - Insiders 1.47.0-insider (7e4cc2c435927e5a2845897961a2af10ee7f784d, 2020-06-12T06:03:53.183Z) OS version: Windows_NT x64 10.0.19041

System Info

Item	Value
CPUs	Intel® Core™ i5-1035G7 CPU @ 1.20GHz (8 x 1498)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on oop_rasterization: disabled_off protected_video_decode: enabled rasterization: enabled skia_renderer: disabled_off_ok video_decode: enabled viz_display_compositor: enabled_on viz_hit_test_surface_layer: disabled_off_ok webgl: enabled webgl2: enabled
Load (avg)	undefined
Memory (System)	7.60GB (0.41GB free)
Process Argv
Screen Reader	no
VM	0%

Issue Analytics

State:
Created 3 years ago
Comments:6 (4 by maintainers)

Top GitHub Comments

2reactions

andschwacommented, May 25, 2021

This is by design; once an extension sets a title it cannot be unset. The terminal title is determined by the following priority:

An extension has set it

A process has set it with terminal.integrated.experimentalUseTitleEvent set to true

The shell title is pulled from the process name (which process it gets it from is a little complicated)

Currently you can’t do anything here but I’m open to suggestions to change how it works 🤔

This being the case, I’m going to close this issue. Thanks for the information 😁

2reactions

JustinGrotecommented, Jun 13, 2020

I would say this is an extremely low priority item, the use cases I can think of can pretty well just be communicated at the console, and you make a good point that the integrated can stay that and other terms can retitle themselves (e.g. Remoting to another system)

Top Results From Across the Web

How to change default terminal in VS Code - Stack Overflow

When terminal is opened, in top right corner user should click on down-arrow button and then an option menu will appear.

Developing in WSL - Visual Studio Code

Open a WSL terminal window (using the start menu item or by typing wsl from a command prompt / PowerShell). Navigate to a...

Windows Terminal as your Default Command Line Experience

A default terminal is the terminal emulator that launches by default when opening a command line application. Starting from the dawn of Windows, ......

Issues with VS Code “PowerShell Integrated” feature

You can change the Terminal Integrated behavior to run other type of console: Bash, DOS, and even PowerShell version X as a standalone...

Make PowerShell and PowerShell Integrated Terminal in VS ...

PowerShell open as an administrator with the warning of script execution is disabled. Run the command Set-ExcecutionPolicy Unrestricted so ...