Invalid Title after opening new tab via command line #13134

Closed
opened 2026-01-31 03:34:42 +00:00 by claunia · 3 comments
Owner

Originally created by @denis-taran on GitHub (Mar 22, 2021).

Windows Terminal version (or Windows build number)

10.0.19042.0

Other Software

Installed WSL Version 2 with Ubuntu Disto

Steps to reproduce

  1. Install WT, WSL2 and Ubuntu as Disto

  2. Set Ubuntu as Default for WT in settings.json

  3. Open a new tab with Powershell and enter the following command:

    wt --% new-tab powershell

Expected Behavior

The first tab in the new window should be called "Windows Powershell", because it is a powershell console

Actual Behavior

It shows that Ubuntu is started and that's not the case. The icon is also wrong.

WT-bug

Originally created by @denis-taran on GitHub (Mar 22, 2021). ### Windows Terminal version (or Windows build number) 10.0.19042.0 ### Other Software Installed WSL Version 2 with Ubuntu Disto ### Steps to reproduce 1. Install WT, WSL2 and Ubuntu as Disto 2. Set Ubuntu as Default for WT in settings.json 3. Open a new tab with Powershell and enter the following command: wt --% new-tab powershell ### Expected Behavior The first tab in the new window should be called "Windows Powershell", because it is a powershell console ### Actual Behavior It shows that Ubuntu is started and that's not the case. The icon is also wrong. ![WT-bug](https://user-images.githubusercontent.com/16059078/111929847-cf823f80-8ab7-11eb-9d0d-021d88fdf04e.gif)
claunia added the Resolution-Duplicate label 2026-01-31 03:34:42 +00:00
Author
Owner

@DHowett commented on GitHub (Mar 22, 2021):

This is just another instance of "the provided commandline replaces the commandline from the default profile". I believe we have an issue tracking this elsewhere on the repository.

The "right" way (today, and until we get executable->profile mapping) to launch this profile is to run wt -p "Windows PowerShell" (or whatever you've named the profile for powershell). Otherwise, your request is "take my default profile, with all of its options like color, title, icon, name, etc. and run powershell inside it."

@DHowett commented on GitHub (Mar 22, 2021): This is just another instance of "the provided commandline _replaces the commandline from the default profile_". I believe we have an issue tracking this elsewhere on the repository. The "right" way (today, and until we get executable->profile mapping) to launch this profile is to run `wt -p "Windows PowerShell"` (or whatever you've named the _profile_ for powershell). Otherwise, your request is "take my default profile, with all of its options like color, title, icon, name, etc. and run powershell inside it."
Author
Owner

@DHowett commented on GitHub (Mar 22, 2021):

Found it! This is a /duplicate of #7552. Thanks!

@DHowett commented on GitHub (Mar 22, 2021): Found it! This is a /duplicate of #7552. Thanks!
Author
Owner

@ghost commented on GitHub (Mar 22, 2021):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Mar 22, 2021): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#13134