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

Settings: Add links to documentation in the settings UI #13441

New Issue
Closed
opened 2026-01-31 03:42:48 +00:00 by claunia · 4 comments
claunia commented 2026-01-31 03:42:48 +00:00
Owner
Copy Link

Originally created by @Armin2208 on GitHub (Apr 14, 2021).

The new Windows Terminal version has a settings UI. Great! But in a regular/typical window size it contains too much blank space, as you can see in the screenshot below.

image

I mostly use my Terminal in a medium size to complete quick tasks. Maximizing or resizing the window just to have a better view of settings is inconvenient.

  • Add help links or link to documentation at the right side, just like system settings.
  • Make the footer smaller.

My idea would be to expand the hamburger menu much sooner at smaller window sizes. Like showing it already on the 120x30 size. Because the main content of the settings doesn't fill much area in the width anyways. This is the minimum size to have an always expanded hamburger menu and you can see: there is still room left.
image

My screenresolution is 2736x1824 and I use 200% scaling (device: Surface Pro 7).

Originally created by @Armin2208 on GitHub (Apr 14, 2021). The new Windows Terminal version has a settings UI. Great! But in a regular/typical window size it contains too much blank space, as you can see in the screenshot below. ![image](https://user-images.githubusercontent.com/32982430/114781237-b7c96e80-9d78-11eb-80e3-638ff5c3c8f7.png) I mostly use my Terminal in a medium size to complete quick tasks. Maximizing or resizing the window just to have a better view of settings is inconvenient. - [ ] Add help links or link to documentation at the right side, just like system settings. - [ ] Make the footer smaller. ~~My idea would be to expand the hamburger menu much sooner at smaller window sizes. Like showing it already on the 120x30 size. Because the main content of the settings doesn't fill much area in the width anyways. This is the minimum size to have an always expanded hamburger menu and you can see: there is still room left.~~ ![image](https://user-images.githubusercontent.com/32982430/114782148-e431ba80-9d79-11eb-9fbc-7c8f2a3d98e9.png) My screenresolution is 2736x1824 and I use 200% scaling (device: Surface Pro 7).
claunia commented 2026-01-31 03:42:50 +00:00
Author
Owner
Copy Link

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

@cinnamon-msft this seems like a question up your alley

@zadjii-msft commented on GitHub (Apr 14, 2021): @cinnamon-msft this seems like a question up your alley
claunia commented 2026-01-31 03:42:50 +00:00
Author
Owner
Copy Link

@cinnamon-msft commented on GitHub (Apr 15, 2021):

We could possibly shrink the size of the footer for a more compact look. We're following the UWP design guidelines when it comes to the main page content. We are planning to add helpful links to the right side of the pages, to help fill in the space and provide links to documentation.

Maybe this issue can be repurposed to: "Add links to documentation in the settings UI" ?

@cinnamon-msft commented on GitHub (Apr 15, 2021): We could possibly shrink the size of the footer for a more compact look. We're following the UWP design guidelines when it comes to the main page content. We are planning to add helpful links to the right side of the pages, to help fill in the space and provide links to documentation. Maybe this issue can be repurposed to: "Add links to documentation in the settings UI" ?
claunia commented 2026-01-31 03:42:50 +00:00
Author
Owner
Copy Link

@Armin2208 commented on GitHub (Apr 16, 2021):

Hi!

Shrinking the footer would be a great step forward :)

It's important to follow the UWP design guidelines, I understand. So there's nothing we can change about this. But it's still sad to have so much space in the settings, just because the hamburger menu is shrinking down too early. And I don't think having a three columns UI makes the app great for users (same goes for windows settings btw).

But hey, it would fit to the settings app and microsoft style, so we can rename this issue.

@Armin2208 commented on GitHub (Apr 16, 2021): Hi! Shrinking the footer would be a great step forward :) It's important to follow the UWP design guidelines, I understand. So there's nothing we can change about this. But it's still sad to have so much space in the settings, just because the hamburger menu is shrinking down too early. And I don't think having a three columns UI makes the app great for users (same goes for windows settings btw). But hey, it would fit to the settings app and microsoft style, so we can rename this issue.
claunia commented 2026-01-31 03:42:50 +00:00
Author
Owner
Copy Link

@Armin2208 commented on GitHub (Sep 6, 2022):

Closed, because new Settings UI doesn't need this

@Armin2208 commented on GitHub (Sep 6, 2022): Closed, because new Settings UI doesn't need this
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 Area-SettingsUI Help Wanted Issue-Task Needs-Tag-Fix Priority-3 Product-Terminal
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#13441
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?