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

click on subdirectory name to change to that directory #13236

New Issue
Closed
opened 2026-01-31 03:37:26 +00:00 by claunia · 2 comments
claunia commented 2026-01-31 03:37:26 +00:00
Owner
Copy Link

Originally created by @cmruffin on GitHub (Mar 30, 2021).

Description of the new feature/enhancement

I work with deep subdirectories of source code. When working in these source trees, I am giving myself carpal tunnel typing cd ........... . It would be fantastic! If you could click on the name of a subdirectory to change to that directory.

Originally created by @cmruffin on GitHub (Mar 30, 2021). # Description of the new feature/enhancement I work with deep subdirectories of source code. When working in these source trees, I am giving myself carpal tunnel typing cd ..\..\..\..\..\. . It would be fantastic! If you could click on the name of a subdirectory to change to that directory.
claunia commented 2026-01-31 03:37:28 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 30, 2021):

This is a neat idea! But I wonder, how would it possibly work? The only way I could possibly imagine is with some sort of extension[1] to OSC 8. This extension would let the client app not just specify a URL for a string of text, but also give some sort of string of text that should be input if the user clicks on it.

Then, that would allow the shell application (cmd, powershell, bash, etc) emit each part of a path as a version of this sequence. So cmd would need to emit something like:

^[]9001;1;cd C:\^[\
C:\
^[]9001;1;^[\
^[]9001;1;cd C:\Foo^[\
Foo\
^[]9001;1;^[\
^[]9001;1;cd C:\Foo\Bar^[\
Bar\
^[]9001;1;^[\

(etc)

To identify each part of the path as a link to a different string of input to send. It's UNBELIEVABLY chatty, but I suppose it would work.

Then, we'd also need every shell to them opt-in to sending sequences like these. Which is:

  • 100% impossible for cmd.exe
  • 100% impossible for Windows PowerShell
  • Maybe possible for PowerShell 7+ / PSReadline
  • Unlikely for bash/fish/zsh, unless the user adds them to their .bashrc (or equivalent) themselves

Unless there's an obvious way to do this that I'm missing. The trick here being "Click on a part of a path to go to that directory". It's easy to have a regex that lets you click on a whole path to perform some action in response to that whole path. It's hard(impossible?) to have the regex let you click on a subset of a path, and know the whole path that came before it. We'd somehow need to independently match C:\, C:\Foo, C:\Foo\Bar, C:\Foo\Bar\Baz as four simultaneous matches for the same region of text, and only allow the shortest version to be the clickable one.

I think it's a neat idea, but I'm going to need any sort of technical proposal for achieving this before I'll put it on the backlog.

[1]: by "extension" I mean entirely new sequence

@zadjii-msft commented on GitHub (Mar 30, 2021): This is a neat idea! But I wonder, how would it possibly work? The only way I could possibly imagine is with some sort of extension<sup>[1]</sup> to OSC 8. This extension would let the client app not just specify a URL for a string of text, but also give some sort of string of text that should be input if the user clicks on it. Then, that would allow the shell application (`cmd`, `powershell`, `bash`, etc) emit each part of a path as a version of this sequence. So cmd would need to emit something like: ``` ^[]9001;1;cd C:\^[\ C:\ ^[]9001;1;^[\ ^[]9001;1;cd C:\Foo^[\ Foo\ ^[]9001;1;^[\ ^[]9001;1;cd C:\Foo\Bar^[\ Bar\ ^[]9001;1;^[\ ``` (etc) To identify each part of the path as a link to a different string of input to send. It's UNBELIEVABLY chatty, but I suppose it _would_ work. Then, we'd also need every shell to them opt-in to sending sequences like these. Which is: * 100% impossible for `cmd.exe` * 100% impossible for Windows PowerShell * Maybe possible for PowerShell 7+ / PSReadline * Unlikely for `bash`/`fish`/`zsh`, unless the user adds them to their `.bashrc` (or equivalent) themselves Unless there's an obvious way to do this that I'm missing. The trick here being "Click on a _part_ of a path to go to that directory". It's easy to have a regex that lets you click on a whole path to perform some action in response to that _whole path_. It's hard(<sup>impossible?</sup>) to have the regex let you click on a subset of a path, and know the whole path that came before it. We'd somehow need to independently match `C:\`, `C:\Foo`, `C:\Foo\Bar`, `C:\Foo\Bar\Baz` as four simultaneous matches for the same region of text, and only allow the shortest version to be the clickable one. I think it's a neat idea, but I'm going to need any sort of technical proposal for achieving this before I'll put it on the backlog. <sup>[1]</sup>: by "extension" I mean _entirely new sequence_
claunia commented 2026-01-31 03:37:28 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Apr 3, 2021):

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment.

@ghost commented on GitHub (Apr 3, 2021): This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for **4 days**. It will be closed if no further activity occurs **within 3 days of this comment**.
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-Author-Feedback Needs-Tag-Fix Needs-Triage No-Recent-Activity
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#13236
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?