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

Keyboard navigation of clickable link #9226

New Issue
Closed
opened 2026-01-31 01:49:08 +00:00 by claunia · 3 comments
claunia commented 2026-01-31 01:49:08 +00:00
Owner
Copy Link

Originally created by @mithrandir on GitHub (Jun 24, 2020).

Description of the new feature/enhancement

Keyboard navigation of clickable link in terminal text. Terminal Roadmap v2.0 is describing about clickable link

| Hyperlinking any links that appear in the text buffer. When clicking on the link, the link will open in your default browser.

However, this involves pointing device such as mouse or trackball. I believe many of terminal users love keyboard and it is important to keep using keyboard without switching to pointing device as much as possble.

Proposed technical implementation details (optional)

We may have a command like "NavigateToPreviousClickableLink" or "NavtigateToNextClickableLink" and "InvokeFocusedClickableLink", then we can reassign key binding those command.

bentaudun commented as https://github.com/microsoft/terminal/issues/204#issuecomment-640016016 but wasn't mentioned in https://github.com/microsoft/terminal/issues/574

Originally created by @mithrandir on GitHub (Jun 24, 2020). # Description of the new feature/enhancement Keyboard navigation of clickable link in terminal text. [Terminal Roadmap v2.0](https://github.com/microsoft/terminal/blob/master/doc/terminal-v2-roadmap.md) is describing about clickable link | Hyperlinking any links that appear in the text buffer. When clicking on the link, the link will open in your default browser. However, this involves pointing device such as mouse or trackball. I believe many of terminal users love keyboard and it is important to keep using keyboard without switching to pointing device as much as possble. # Proposed technical implementation details (optional) We may have a command like "NavigateToPreviousClickableLink" or "NavtigateToNextClickableLink" and "InvokeFocusedClickableLink", then we can reassign key binding those command. bentaudun commented as https://github.com/microsoft/terminal/issues/204#issuecomment-640016016 but wasn't mentioned in https://github.com/microsoft/terminal/issues/574
claunia commented 2026-01-31 01:49:09 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jun 24, 2020):

I agree this would be super useful. I'd think we could probably leave out InvokeFocusedClickableLink, and just leave that as space or enter, but now as I'm typing this up, maybe people would want to navigate to the previous link, then copy it, then return to the input line and paste it? So maybe another action for that makes sense? Though, we can't have multiple actions bound to the same key, so that wouldn't work with "enter to copy" people...

I'm maybe rambling a bit.

This is a good idea for inclusion once #574/#204 lands.

@zadjii-msft commented on GitHub (Jun 24, 2020): I agree this would be super useful. I'd think we could probably leave out `InvokeFocusedClickableLink`, and just leave that as <kbd>space</kbd> or <kbd>enter</kbd>, but now as I'm typing this up, maybe people would want to navigate to the previous link, then copy it, then return to the input line and paste it? So maybe another action for that makes sense? Though, we can't have multiple actions bound to the same key, so that wouldn't work with "<kbd>enter</kbd> to copy" people... I'm maybe rambling a bit. This is a good idea for inclusion once #574/#204 lands.
claunia commented 2026-01-31 01:49:10 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (May 16, 2022):

Copying some ideas from the dup I accidentally made...

Description of the new feature/enhancement

Windows Terminal supports automatic detection of hyperlinks and allows you to open the hyperlink using your mouse (specifically ctrl+clicking the link). I've realized that there's no way to do this using only the keyboard.

Once mark mode lands, the solution is a little better, but still far from perfect and on par. The user would be able to navigate to the text with the hyperlink, create a selection that encompasses it, copy the URL, then manually open it in their preferred web browser.

What if we could make this a nicer experience? Consider this...

  1. enter mark mode
  2. tab (or shift+tab) to navigate to these hyperlinks
  3. when you've navigated to the hyperlink, a selection is created that encompasses the relevant hyperlink.
  4. enter can be used to invoke the hyperlink directly

Some corner cases...

  • what if enter is bound to an action (like "copy")? --> prefer the action
  • what if we add more bookmark-like things like "prompt position" or user-configured bookmarks --> might as well navigate to them too? I'm thinking these can be tab stops.

From Mike...

Oh man do I have thoughts in https://github.com/microsoft/terminal/issues/11000.

@carlos-zamora commented on GitHub (May 16, 2022): Copying some ideas from the dup I accidentally made... # Description of the new feature/enhancement Windows Terminal supports automatic detection of hyperlinks and allows you to open the hyperlink using your mouse (specifically ctrl+clicking the link). I've realized that there's no way to do this using only the keyboard. Once mark mode lands, the solution is a little better, but still far from perfect and on par. The user would be able to navigate to the text with the hyperlink, create a selection that encompasses it, copy the URL, then manually open it in their preferred web browser. What if we could make this a nicer experience? Consider this... 1. enter mark mode 2. <kbd>tab</kbd> (or <kbd>shift+tab</kbd>) to navigate to these hyperlinks 3. when you've navigated to the hyperlink, a selection is created that encompasses the relevant hyperlink. 4. <kbd>enter</kbd> can be used to invoke the hyperlink directly Some corner cases... - what if <kbd>enter</kbd> is bound to an action (like "copy")? --> prefer the action - what if we add more bookmark-like things like "prompt position" or user-configured bookmarks --> might as well navigate to them too? I'm thinking these can be tab stops. From Mike... > Oh man do I have thoughts in https://github.com/microsoft/terminal/issues/11000.
claunia commented 2026-01-31 01:49:10 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Sep 13, 2022):

:tada:This issue was addressed in #13405, which has now been successfully released as Windows Terminal Preview v1.16.252.🎉

Handy links:

@ghost commented on GitHub (Sep 13, 2022): :tada:This issue was addressed in #13405, which has now been successfully released as `Windows Terminal Preview v1.16.252`.:tada: Handy links: * [Release Notes](https://github.com/microsoft/terminal/releases/tag/v1.16.252) * [Store Download](https://www.microsoft.com/store/apps/9n8g5rfz9xk3?cid=storebadge&ocid=badge)
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 A11yMAS Area-Input Disability-Mobility InclusionBacklog InclusionBacklog-Windows TerminalWin32 Issue-Feature Issue-Task Product-Terminal Resolution-Fix-Committed
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#9226
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?