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

[PR #2348] [CLOSED] Hot take: we set the tab title for cmd and powershell by default #24893

New Issue
Open
opened 2026-01-31 09:05:58 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 09:05:58 +00:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/microsoft/terminal/pull/2348
Author: @zadjii-msft
Created: 8/8/2019
Status: ❌ Closed

Base: master ← Head: dev/migrie/b/hot-take

📝 Commits (1)

  • 8b43686 Hot take: we set the tab title for cmd and powershell by default

📊 Changes

3 files changed (+8 additions, -0 deletions)

View changed files

📝 src/cascadia/TerminalApp/CascadiaSettings.cpp (+2 -0)
📝 src/cascadia/TerminalApp/Profile.cpp (+5 -0)
📝 src/cascadia/TerminalApp/Profile.h (+1 -0)

📄 Description

I'm submitting this PR to start a discussion about this. If we reach consensus against it, I'm happy to close it. I'm also liking Plan B the more I think on it.

Summary of the Pull Request

We don't set it for WSL, Azure, or Powershell core

Plan B: Add an "initialTabTitle" setting. With that set, we'll ignore the first title conpty sets for us. If conpty sets another title, we'll blow the initial title away and continue using the title from VT. This would be more similar to how cmd and powershell use the title from a shortcut currently.

image

References

literally every issue that mentions the length of the tab title, but #2327 was the one that broke the camel's back.

PR Checklist

  • Closes #the-endless-stream-of-complaints-about-tab-titles
  • CLA signed. If not, go over here and sign the CLA
  • Tests added/passed
  • Requires documentation to be updated - Probably does
  • I have not discussed this with core contributors already.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/microsoft/terminal/pull/2348 **Author:** [@zadjii-msft](https://github.com/zadjii-msft) **Created:** 8/8/2019 **Status:** ❌ Closed **Base:** `master` ← **Head:** `dev/migrie/b/hot-take` --- ### 📝 Commits (1) - [`8b43686`](https://github.com/microsoft/terminal/commit/8b43686715a26a701f4c1bee1f4a037da2af9a34) Hot take: we set the tab title for cmd and powershell by default ### 📊 Changes **3 files changed** (+8 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `src/cascadia/TerminalApp/CascadiaSettings.cpp` (+2 -0) 📝 `src/cascadia/TerminalApp/Profile.cpp` (+5 -0) 📝 `src/cascadia/TerminalApp/Profile.h` (+1 -0) </details> ### 📄 Description I'm submitting this PR to start a discussion about this. If we reach consensus against it, I'm happy to close it. I'm also liking **Plan B** the more I think on it. <!-- Enter a brief description/summary of your PR here. What does it fix/what does it change/how was it tested (even manually, if necessary)? --> ## Summary of the Pull Request We don't set it for WSL, Azure, or Powershell core **Plan B**: Add an `"initialTabTitle"` setting. With that set, we'll ignore the _first_ title conpty sets for us. If conpty sets another title, we'll blow the initial title away and continue using the title from VT. This would be more similar to how cmd and powershell use the title from a shortcut currently. ![image](https://user-images.githubusercontent.com/18356694/62713127-d41ce180-b9c1-11e9-8364-0ffe4d2078cb.png) <!-- Other than the issue solved, is this relevant to any other issues/existing PRs? --> ## References literally every issue that mentions the length of the tab title, but #2327 was the one that broke the camel's back. <!-- Please review the items on the PR checklist before submitting--> ## PR Checklist * [x] Closes #the-endless-stream-of-complaints-about-tab-titles * [x] CLA signed. If not, go over [here](https://cla.opensource.microsoft.com/microsoft/Terminal) and sign the CLA * [ ] Tests added/passed * [ ] Requires documentation to be updated - **Probably does** * [ ] I have **not** discussed this with core contributors already. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
claunia added the pull-request label 2026-01-31 09:05:58 +00:00
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 pull-request
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#24893
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?