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

Default tab title is super-long, only 3 tabs fit the screen #5547

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

Originally created by @vadimkantorov on GitHub (Dec 13, 2019).

On the most recent version from Releases:

image

I'm sure there are reasons why it's like this, but it renders tabs unusable for me in the current state: only three tabs fit the screen at a time.

Yes, I realize this has been discussed before and all previous issues were closed, with issue authors often disagreeing with their closing (sometimes a minor related cause was dealt with, but the original issue still stands). Please feel free to close this as well if the whole long default tab title affair is decided WONTFIX.

Yes, I realize one can probably configure the tab title, but I don't consider this as a valid argument. IMO having to configure such a basic thing is a show-stopper when trying out a new terminal.

The screen is a Surface Pro 7 screen if it matters.

Originally created by @vadimkantorov on GitHub (Dec 13, 2019). On the most recent version from Releases: ![image](https://user-images.githubusercontent.com/1041752/70765017-1dab7d80-1d62-11ea-9818-598002e6d6cb.png) I'm sure there are reasons why it's like this, but it renders tabs unusable for me in the current state: only three tabs fit the screen at a time. Yes, I realize this has been discussed before and all previous issues were closed, with issue authors often disagreeing with their closing (sometimes a minor related cause was dealt with, but the original issue still stands). Please feel free to close this as well if the whole long default tab title affair is decided WONTFIX. Yes, I realize one can probably configure the tab title, but I don't consider this as a valid argument. IMO having to configure such a basic thing is a show-stopper when trying out a new terminal. The screen is a Surface Pro 7 screen if it matters.
claunia added the Resolution-Duplicate label 2026-01-31 00:15:52 +00:00
claunia commented 2026-01-31 00:15:53 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Dec 13, 2019):

Two things, actually:

  1. that tab title was generated by your shell, and is configurable in your shell's startup scripts (for bash, that's probably /etc/profile). you can actually configure it to contain anything you want, which is really cool. I know you already enumerated this as an option, but it really is the "best" fix ;P
  2. not all previous issues were closed, actually: this is largely a /dupe of #597 (which is very much still open) 😄
@DHowett-MSFT commented on GitHub (Dec 13, 2019): Two things, actually: 1. that tab title was generated by your shell, and is configurable in your shell's startup scripts (for bash, that's probably `/etc/profile`). you can actually configure it to contain anything you want, which is really cool. I know you already enumerated this as an option, but it really is the "best" fix ;P 2. not all previous issues were closed, actually: this is largely a /dupe of #597 (which is very much still open) :smile:
claunia commented 2026-01-31 00:15:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 13, 2019):

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 (Dec 13, 2019): 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!
claunia commented 2026-01-31 00:15:53 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Dec 13, 2019):

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 (Dec 13, 2019): 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!
claunia commented 2026-01-31 00:15:54 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Dec 13, 2019):

  1. Well, then please put it in Top of readme, in a popping message box, tooltip or whatever popping into eyes. If I happen to have a long username and a long computer name, Windows Terminal is taxing me by a lot of time figuring out how to reset this. Of course I realize that current tab title is provided by the bash profile, but I don’t think the tab title is informative

  2. I hope that 2 is resolved before 1.0 release

@vadimkantorov commented on GitHub (Dec 13, 2019): 1. Well, then please put it in Top of readme, in a popping message box, tooltip or whatever popping into eyes. If I happen to have a long username and a long computer name, Windows Terminal is taxing me by a lot of time figuring out how to reset this. Of course I realize that current tab title is provided by the bash profile, but I don’t think the tab title is informative 2. I hope that 2 is resolved before 1.0 release
claunia commented 2026-01-31 00:15:54 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Dec 13, 2019):

Sorry, https://github.com/microsoft/terminal/issues/597 is vague. It starts by asking for min-width. Then someone suggests it would be good to have max-width, but it is not clearly stated in the OP.

Could you please keep this issue open until something in the underlying tab control gets fixed and then the user-facing problem described in this issue (https://github.com/microsoft/terminal/issues/597 is more about impl details) has an official default solution?

@vadimkantorov commented on GitHub (Dec 13, 2019): Sorry, https://github.com/microsoft/terminal/issues/597 is vague. It starts by asking for min-width. Then someone suggests it would be good to have max-width, but it is not clearly stated in the OP. Could you please keep this issue open until something in the underlying tab control gets fixed and then the user-facing problem described in this issue (https://github.com/microsoft/terminal/issues/597 is more about impl details) has an official default solution?
claunia commented 2026-01-31 00:15:54 +00:00
Author
Owner
Copy Link

@vadimkantorov commented on GitHub (Dec 13, 2019):

https://github.com/microsoft/terminal/pull/3876 Work seems actively progressing, I hope it gets merged before 1.0 and equal mode is enabled by default. Pretty much everyone would be surprised that WT doesn’t handle tabs like web browser or supports only three tabs visible (without having to reset bash profile env variables)

@vadimkantorov commented on GitHub (Dec 13, 2019): https://github.com/microsoft/terminal/pull/3876 Work seems actively progressing, I hope it gets merged before 1.0 and equal mode is enabled by default. Pretty much everyone would be surprised that WT doesn’t handle tabs like web browser or supports only three tabs visible (without having to reset bash profile env variables)
claunia commented 2026-01-31 00:15:55 +00:00
Author
Owner
Copy Link

@navossoc commented on GitHub (Dec 13, 2019):

@vadimkantorov Yes, I agree, three tabs is really bad...
Also if you maximize the window you can't get pass of three tabs (which really sucks).

Until #3876 was not merged, I did override the title of the tab on the terminal settings, using name and suppressApplicationTitle properties on profiles array.

image

For now, I can have at least 7 (full) tabs.
This was the easiest and cleanly way I found to do that.

I hope this be addressed in the future.

@navossoc commented on GitHub (Dec 13, 2019): @vadimkantorov Yes, I agree, three tabs is really bad... Also if you maximize the window you can't get pass of three tabs (which really sucks). Until #3876 was not merged, I did override the title of the tab on the terminal settings, using `name` and `suppressApplicationTitle` properties on `profiles` array. ![image](https://user-images.githubusercontent.com/2457338/70771160-e1baed00-1d4e-11ea-9a15-926fd6c3684d.png) For now, I can have at least 7 (full) tabs. This was the easiest and cleanly way I found to do that. I hope this be addressed in the future.
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 Resolution-Duplicate
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#5547
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?