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

Getting an complete folder structure in terminal only(Different colour structure) #20175

New Issue
Closed
opened 2026-01-31 07:05:44 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 07:05:44 +00:00
Owner
Copy Link

Originally created by @anuraghit on GitHub (Jul 1, 2023).

Description of the new feature/enhancement

I am writing today to make a feature request that I believe would greatly enhance the user experience for developers working in the terminal. Currently, when navigating through repositories in the terminal, the folder structure is displayed in a uniform color, making it challenging to quickly identify different levels and subdirectories.

I would like to propose the implementation of a feature that allows for a complete folder structure to be displayed in the terminal, with each level of the structure assigned a distinct color. This visual differentiation would enable developers to easily grasp the hierarchy of their project and navigate through directories more efficiently.

I believe that this feature would be highly beneficial to developers who frequently work in the terminal, helping them save time and reduce errors. It would greatly enhance the productivity and user experience for GitHub users across the globe.

Thank you for considering my feature request. I appreciate the hard work and dedication of the GitHub team in continuously improving the platform. I look forward to seeing GitHub evolve and empower developers even further.

Proposed technical implementation details (optional)

Originally created by @anuraghit on GitHub (Jul 1, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement I am writing today to make a feature request that I believe would greatly enhance the user experience for developers working in the terminal. Currently, when navigating through repositories in the terminal, the folder structure is displayed in a uniform color, making it challenging to quickly identify different levels and subdirectories. I would like to propose the implementation of a feature that allows for a complete folder structure to be displayed in the terminal, with each level of the structure assigned a distinct color. This visual differentiation would enable developers to easily grasp the hierarchy of their project and navigate through directories more efficiently. I believe that this feature would be highly beneficial to developers who frequently work in the terminal, helping them save time and reduce errors. It would greatly enhance the productivity and user experience for GitHub users across the globe. Thank you for considering my feature request. I appreciate the hard work and dedication of the GitHub team in continuously improving the platform. I look forward to seeing GitHub evolve and empower developers even further. # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureNeeds-TriageNeeds-Tag-Fix labels 2026-01-31 07:05:45 +00:00
claunia commented 2026-01-31 07:05:46 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jul 5, 2023):

This is usually something configurable based on the application that's emitting the directory structure. For example, ls uses LS_COLORS to change the colors of the output based on the file type. There's a similar way of controlling the colors in PowerShell 7.2+.

Terminal is more than happy to listen to the colors emitted by an app, but we don't really control what the client application chooses to emit.

@zadjii-msft commented on GitHub (Jul 5, 2023): This is usually something configurable based on the application that's emitting the directory structure. For example, `ls` uses `LS_COLORS` to change the colors of the output based on the file type. There's a similar way of [controlling the colors in PowerShell 7.2+](https://superuser.com/a/1761384). Terminal is more than happy to listen to the colors emitted by an app, but we don't really control what the client application chooses to emit.
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-Feature 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#20175
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?