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

FR: Marks for easy navigation like Terminal.app #6827

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

Originally created by @jkuebart on GitHub (Mar 11, 2020).

Description of the new feature/enhancement

I would really like to see a feature I use heavily when working on the command line in Terminal.app on macOS: marks.

When pressing enter, the current line is automatically »marked«. Visually, this is indicated by little brackets on the side of the line – but that's not the interesting/useful part: subsequently, it's possible to navigate between these lines using Command-↑ and Command-↓, among other things. The marked lines scroll into view, making it very convenient to navigate the terminal's back buffer.

This is very useful when programs produce long outputs, such as the debugger lldb: simply press Command-↑ and you see the top of the list and can then scroll back down using scroll bars, mouse wheel, whatever…

Another really nice feature is Command-Shift-A which selects the text up to the most recently marked line: for example, one can simply type »ls« enter, Command-Shift-A Command-C, which selects the output of the command and copies it to the clipboard.

Proposed technical implementation details (optional)

I have no idea how it could be implemented in practice, but it doesn't feel like a very big feature. I think that the visual feedback is secondary, just marking a line automatically after hitting enter already covers 99% of use cases.

The most important keyboard shortcuts are »up« and »down« to scroll the back buffer between the marks. The second most important shortcut is to select from the current position to the most recent mark, but even that could be implemented as a second step.

Terminal.app has more features such as marking manually, bookmarks &c which I have never used, so seems comparatively unimportant.

Originally created by @jkuebart on GitHub (Mar 11, 2020). # Description of the new feature/enhancement I would really like to see a feature I use heavily when working on the command line in Terminal.app on macOS: marks. When pressing enter, the current line is automatically »marked«. Visually, this is indicated by little brackets on the side of the line – but that's not the interesting/useful part: subsequently, it's possible to navigate between these lines using Command-↑ and Command-↓, among other things. The marked lines scroll into view, making it very convenient to navigate the terminal's back buffer. This is very useful when programs produce long outputs, such as the debugger lldb: simply press Command-↑ and you see the top of the list and can then scroll back down using scroll bars, mouse wheel, whatever… Another really nice feature is Command-Shift-A which selects the text up to the most recently marked line: for example, one can simply type »ls« enter, Command-Shift-A Command-C, which selects the output of the command and copies it to the clipboard. # Proposed technical implementation details (optional) I have no idea how it could be implemented in practice, but it doesn't feel like a very big feature. I think that the visual feedback is secondary, just marking a line automatically after hitting enter already covers 99% of use cases. The most important keyboard shortcuts are »up« and »down« to scroll the back buffer between the marks. The second most important shortcut is to select from the current position to the most recent mark, but even that could be implemented as a second step. Terminal.app has more features such as marking manually, bookmarks &c which I have never used, so seems comparatively unimportant.
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 00:48:11 +00:00
claunia commented 2026-01-31 00:48:12 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Mar 11, 2020):

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1527 for more discussion.

/dup #1527

@zadjii-msft commented on GitHub (Mar 11, 2020): Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #1527 for more discussion. /dup #1527
claunia commented 2026-01-31 00:48:13 +00:00
Author
Owner
Copy Link

@ghost commented on GitHub (Mar 11, 2020):

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 (Mar 11, 2020): 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:48:13 +00:00
Author
Owner
Copy Link

@DHowett-MSFT commented on GitHub (Mar 11, 2020):

There's no explicit note about inserting a mark when you press Enter in that bug, but it does mention prompt positions so I believe it's sufficient. Thanks!

@DHowett-MSFT commented on GitHub (Mar 11, 2020): There's no explicit note about inserting a mark when you press <kbd>Enter</kbd> in that bug, but it _does_ mention prompt positions so I believe it's sufficient. Thanks!
claunia commented 2026-01-31 00:48:14 +00:00
Author
Owner
Copy Link

@jkuebart commented on GitHub (Mar 11, 2020):

@DHowett-MSFT I briefly looked at #1527 but that looked like it's just about visual cues on the scrollbar rather than navigation shortcuts. I see now that keyboard bindings are mentioned in a comment, so I'm taking the liberty to add my suggestions on that ticket as well.

@jkuebart commented on GitHub (Mar 11, 2020): @DHowett-MSFT I briefly looked at #1527 but that looked like it's just about visual cues on the scrollbar rather than navigation shortcuts. I see now that keyboard bindings *are* mentioned in a comment, so I'm taking the liberty to add my suggestions on that ticket as well.
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 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#6827
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?