starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-03 21:25:34 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Setting title of a split-pane tab via cli only sets title when pane is active #16738

New Issue
Closed
opened 2026-01-31 05:21:18 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 05:21:18 +00:00
Owner
Copy Link

Originally created by @joshuacookdev on GitHub (Feb 10, 2022).

Windows Terminal version

1.11.3471.0

Windows build number

10.0.22000.493

Other Software

Using PowerShell Core (7.2.1) as default profile.

Steps to reproduce

Run the following command in PS (any directory will work):

wt -w 0 nt --title Test -d C:/Users `; sp -d C:/Windows

(with or without the `; will work afaik)

Expected Behavior

The tab to have the title "Test" regardless of which pane is focused in that tab, the same behavior as if I manually named the tab by double-clicking and typing the name.

I skimmed the MS Docs page again to confirm that this should set the tab title. I also tried adding a split pane in a few places to the command example and am seeing the same behavior. If there's a different syntax for setting the Tab title (and the --title flag is meant to be pane title), then this should maybe be a documentation issue instead of a bug?

I'm not sure what "right" looks like for this (whether it's a behavior change or a syntax/documentation change), so I went with issue-bug rather than another option for the issue type. Feel free to rescope if needed, this isn't necessarily a show-stopper issue for me.

Actual Behavior

When you focus on the left pane (Users directory), the tab has the "Test" title. When you focus on the right pane (Windows directory) the tab title changes to PowerShell.

Placement of the --title command doesn't seem to impact the behavior, unless I'm missing something in the command formatting.

Originally created by @joshuacookdev on GitHub (Feb 10, 2022). ### Windows Terminal version 1.11.3471.0 ### Windows build number 10.0.22000.493 ### Other Software Using PowerShell Core (7.2.1) as default profile. ### Steps to reproduce Run the following command in PS (any directory will work): ``` wt -w 0 nt --title Test -d C:/Users `; sp -d C:/Windows ```` (with or without the `; will work afaik) ### Expected Behavior The tab to have the title "Test" regardless of which pane is focused in that tab, the same behavior as if I manually named the tab by double-clicking and typing the name. I skimmed [the MS Docs page](https://docs.microsoft.com/en-us/windows/terminal/command-line-arguments?tabs=powershell#tab-title) again to confirm that this *should* set the tab title. I also tried adding a split pane in a few places to the command example and am seeing the same behavior. If there's a different syntax for setting the Tab title (and the --title flag is meant to be pane title), then this should *maybe* be a documentation issue instead of a bug? I'm not sure what "right" looks like for this (whether it's a behavior change or a syntax/documentation change), so I went with issue-bug rather than another option for the issue type. Feel free to rescope if needed, this isn't necessarily a show-stopper issue for me. ### Actual Behavior When you focus on the left pane (`Users` directory), the tab has the "Test" title. When you focus on the right pane (`Windows` directory) the tab title changes to PowerShell. Placement of the `--title` command doesn't seem to impact the behavior, unless I'm missing something in the command formatting.
claunia added the Issue-BugResolution-ExternalNeeds-Tag-Fix labels 2026-01-31 05:21:19 +00:00
claunia commented 2026-01-31 05:21:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 10, 2022):

That's maybe a bit confusing. Each pane has its own "title". The --title arg on the first nt command sets the tab title for the first pane, but not the second one.

@zadjii-msft commented on GitHub (Feb 10, 2022): That's maybe a bit confusing. Each pane has its own "title". The `--title` arg on the first `nt` command sets the tab title for the first pane, but not the second one.
claunia commented 2026-01-31 05:21:20 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Feb 10, 2022):

I'm gonna move this to a docs bug over at /dup https://github.com/MicrosoftDocs/terminal/issues/499. Sorry for the confusion!

@zadjii-msft commented on GitHub (Feb 10, 2022): I'm gonna move this to a docs bug over at /dup https://github.com/MicrosoftDocs/terminal/issues/499. Sorry for the confusion!
claunia commented 2026-01-31 05:21:20 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Feb 10, 2022):

Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!

@ghost commented on GitHub (Feb 10, 2022): Hi! We've identified this issue as a duplicate of one that exists on somebody else's Issue Tracker. Please make sure you subscribe to the referenced external issue for future updates. Thanks for your report!
claunia commented 2026-01-31 05:21:20 +00:00
Author
Owner
Copy Link

@joshuacookdev commented on GitHub (Feb 10, 2022):

@zadjii-msft thanks for the clarification - part of me had thought the "per pane tab title" was intentional, but the docs weren't super clear on the matter.

Question: Is there currently an option to set the tab title via the cli (that behaves the same as manually setting the tab title)? If not, would it be possible to convert this issue-bug into a feature request (maybe saying --tab-title sets title for entire tab)? I'd be willing to attempt the work if it's something the team would be interested in having as a cli flag. I'm good with the behavior as-is, though - I'll just duplicate the --title flag in my shortcuts.

@joshuacookdev commented on GitHub (Feb 10, 2022): @zadjii-msft thanks for the clarification - part of me had thought the "per pane tab title" was intentional, but the docs weren't super clear on the matter. Question: Is there currently an option to set the tab title via the cli (that behaves the same as manually setting the tab title)? If not, would it be possible to convert this issue-bug into a feature request (maybe saying `--tab-title` sets title for entire tab)? I'd be willing to attempt the work if it's something the team would be interested in having as a cli flag. I'm good with the behavior as-is, though - I'll just duplicate the --title flag in my shortcuts.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Issue-Bug Needs-Tag-Fix Resolution-External
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#16738
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?