Vscode-powershell: [Insiders] Cannot change Terminal Name from "Powershell Integrated Console"

Created on 13 Jun 2020  路  6Comments  路  Source: PowerShell/vscode-powershell

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.

image

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(R) Core(TM) 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%|


Area-Integrated Console Issue-Discussion Resolution-Answered

Most helpful comment

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

  1. An extension has set it
  2. A process has set it with terminal.integrated.experimentalUseTitleEvent set to true
  3. 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 馃榿

All 6 comments

I have a feeling that I might need guidance from @Tyriar for this one. How can I support this?

@TylerLeonhardt not entirely sure it "overrides" per se, maybe it just never makes the roundtrip back from PSES back to the xterm title API?

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

  1. An extension has set it
  2. A process has set it with terminal.integrated.experimentalUseTitleEvent set to true
  3. 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 馃

I don't know... I mean. @JustinGrote is there a scenario here you have in mind? I don't want people to forget which one is the Integrated Console 馃槄

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)

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

  1. An extension has set it
  2. A process has set it with terminal.integrated.experimentalUseTitleEvent set to true
  3. 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 馃榿

Was this page helpful?
0 / 5 - 0 ratings

Related issues

nathan-alden-hp picture nathan-alden-hp  路  3Comments

timoline picture timoline  路  3Comments

MiYanni picture MiYanni  路  3Comments

inthemedium picture inthemedium  路  3Comments

rkeithhill picture rkeithhill  路  3Comments