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

Folder Name as Tab Title #13273

New Issue
Closed
opened 2026-01-31 03:38:21 +00:00 by claunia · 7 comments
claunia commented 2026-01-31 03:38:21 +00:00
Owner
Copy Link

Originally created by @tylerthrash on GitHub (Apr 1, 2021).

Please add a setting to have the tab title be the folder name. Ideally as (shell). Currently for me it just shows the shell title.

For example, if I have a PowerShell Core instance open in myApp folder then have the tab title be: "myApp (PowerShell)" or simply "myApp".

There's possibly an existing way to do this, but what I'm suggesting is to have an easy setting instead.

Originally created by @tylerthrash on GitHub (Apr 1, 2021). Please add a setting to have the tab title be the folder name. Ideally as <folder name>(shell). Currently for me it just shows the shell title. For example, if I have a PowerShell Core instance open in myApp folder then have the tab title be: "myApp (PowerShell)" or simply "myApp". There's possibly an existing way to do this, but what I'm suggesting is to have an easy setting instead.
claunia added the Needs-TriageNeeds-Tag-Fix labels 2026-01-31 03:38:21 +00:00
claunia commented 2026-01-31 03:38:22 +00:00
Author
Owner
Copy Link

@WSLUser commented on GitHub (Apr 1, 2021):

Please check the docs before filing issues like this: https://docs.microsoft.com/en-us/windows/terminal/tutorials/tab-title

@WSLUser commented on GitHub (Apr 1, 2021): Please check the docs before filing issues like this: https://docs.microsoft.com/en-us/windows/terminal/tutorials/tab-title
claunia commented 2026-01-31 03:38:22 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 1, 2021):

Yup! This is totally possible with the cooperation of your shell.

@DHowett commented on GitHub (Apr 1, 2021): Yup! This is totally possible with the cooperation of your shell.
claunia commented 2026-01-31 03:38:23 +00:00
Author
Owner
Copy Link

@tylerthrash commented on GitHub (Apr 1, 2021):

I did see those docs, but I was wondering if there was an way that the tab title could be set with a simple, universal setting in Windows Terminal. This was rather a feature request. Such as having tabTitle configurations (for example, static string, absolute path, relative path), and based on the shell instance have code within Windows Terminal to do that for the most popular shells.

For anyone wondering I was able to set this up for PowerShell Core shell by adding the following code to my PowerShell Core profile in Documents\PowerShell\Microsoft.PowerShell_profile.ps1

function Prompt
{
  $host.UI.RawUI.WindowTitle = Split-Path (Get-Location) -Leaf
}
@tylerthrash commented on GitHub (Apr 1, 2021): I did see those docs, but I was wondering if there was an way that the tab title could be set with a simple, universal setting in Windows Terminal. This was rather a feature request. Such as having tabTitle configurations (for example, static string, absolute path, relative path), and based on the shell instance have code within Windows Terminal to do that for the most popular shells. For anyone wondering I was able to set this up for PowerShell Core shell by adding the following code to my PowerShell Core profile in `Documents\PowerShell\Microsoft.PowerShell_profile.ps1` ``` function Prompt { $host.UI.RawUI.WindowTitle = Split-Path (Get-Location) -Leaf } ```
claunia commented 2026-01-31 03:38:23 +00:00
Author
Owner
Copy Link

@DHowett commented on GitHub (Apr 1, 2021):

I'd love for us to offer this, but unfortunately it's difficult for Terminal to know what folder you're operating in. PowerShell doesn't update its process-level working directory; SSH targets a remote machine; you might have run a shell inside your shell (cmd -> wsl; which one should it report? what if you're running wmic and it changes to system32 just because?); WSL operates in a totally different filesystem environment;

The list goes on. We have a couple other things that would depend on the active working directory path that we'd love to land . . . but unfortunately we don't think we can.

@DHowett commented on GitHub (Apr 1, 2021): I'd love for us to offer this, but unfortunately it's difficult for Terminal to know what folder you're operating in. PowerShell doesn't update its process-level working directory; SSH targets a remote machine; you might have run a shell inside your shell (`cmd` -> `wsl`; which one should it report? what if you're running `wmic` and it changes to system32 _just because_?); WSL operates in a totally different filesystem environment; The list goes on. We have a couple other things that would depend on the active working directory path that we'd love to land . . . but unfortunately we don't think we can.
claunia commented 2026-01-31 03:38:23 +00:00
Author
Owner
Copy Link

@tylerthrash commented on GitHub (Apr 2, 2021):

That's unfortunate, but makes sense.

Maybe there could be some sort of api standards in the shell world to work with tools like Terminal better. I'm not sure if that would make sense or not, but if anyone could make that happen it would be a company like Microsoft. I guarantee Terminal is going to be hugely popular over time, so there would be leverage in that as well.

Thank you for your quick responses, and keep up the great work!

@tylerthrash commented on GitHub (Apr 2, 2021): That's unfortunate, but makes sense. Maybe there could be some sort of api standards in the shell world to work with tools like Terminal better. I'm not sure if that would make sense or not, but if anyone could make that happen it would be a company like Microsoft. I guarantee Terminal is going to be hugely popular over time, so there would be leverage in that as well. Thank you for your quick responses, and keep up the great work!
claunia commented 2026-01-31 03:38:23 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Apr 2, 2021):

Maybe there could be some sort of api standards in the shell world to work with tools like Terminal better

FYI there is such a "standard", called Escape Sequences (also ANSI escape sequences, VT sequences). See this page for probably the most complete documentation. A shell can already use VT sequences to tell a terminal emulator to do all sorts of things,. For examplem, setting the title of the window with \e]0;YourTitleHere\a, which is exactly what we recommend doing 😉

@zadjii-msft commented on GitHub (Apr 2, 2021): > Maybe there could be some sort of api standards in the shell world to work with tools like Terminal better FYI there is such a "standard", called Escape Sequences (also ANSI escape sequences, VT sequences). See [this page](https://invisible-island.net/xterm/ctlseqs/ctlseqs.html#h3-Operating-System-Commands) for probably the most complete documentation. A shell can already use VT sequences to tell a terminal emulator to do all sorts of things,. For examplem, setting the title of the window with `\e]0;YourTitleHere\a`, which is [exactly what we recommend](https://docs.microsoft.com/en-us/windows/terminal/tutorials/tab-title#set-the-shells-title) doing 😉
claunia commented 2026-01-31 03:38:24 +00:00
Author
Owner
Copy Link

@catamphetamine commented on GitHub (Apr 29, 2021):

The list goes on.

Then it would be easier to have a page in the docs describing how to set up "Folder Name as Tab Name" for each popular shell.

No, I won't be writing something like that. I don't currently use this application.

@catamphetamine commented on GitHub (Apr 29, 2021): > The list goes on. Then it would be easier to have a page in the docs describing how to set up "Folder Name as Tab Name" for each popular shell. No, I won't be writing something like that. I don't currently use this application.
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 Needs-Tag-Fix Needs-Triage
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#13273
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?