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

Moving the Mark-Mode cursor using the find or marks capabilities #23623

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

Originally created by @varzenbot on GitHub (Sep 17, 2025).

Originally assigned to: @carlos-zamora on GitHub.

Description of the new feature

Hello,

I'm using the windows terminal to ssh into other machines and run commands there that return large amounts of output.

Sometimes I want to go select some text from said output and copy it to place it inside an e-mail or teams window to share with colleagues. So I enter into Mark-Mode, but that moves the viewport to the end of the terminal, and forces me to move the mark-mode cursor using page-up until I reach back to the area of interest, which is sometimes hard to see in the large amounts of text.
What I try to do is use find and place a mark there that I reference when moving the cursor back.

Is it possible to have the Mark-Mode cursor be moved by find, or perhaps have it movable to previous marks, and using the arrow keys to refine the selection process.

I have been using the find capability and the mouse so far, but would love to be able to perform this using only the keyboard.

Kind regards!

Windows Terminal
Version: 1.22.12111.0

Proposed technical implementation details

No response

Originally created by @varzenbot on GitHub (Sep 17, 2025). Originally assigned to: @carlos-zamora on GitHub. ### Description of the new feature Hello, I'm using the windows terminal to ssh into other machines and run commands there that return large amounts of output. Sometimes I want to go select some text from said output and copy it to place it inside an e-mail or teams window to share with colleagues. So I enter into Mark-Mode, but that moves the viewport to the end of the terminal, and forces me to move the mark-mode cursor using page-up until I reach back to the area of interest, which is sometimes hard to see in the large amounts of text. What I try to do is use find and place a mark there that I reference when moving the cursor back. Is it possible to have the Mark-Mode cursor be moved by find, or perhaps have it movable to previous marks, and using the arrow keys to refine the selection process. I have been using the find capability and the mouse so far, but would love to be able to perform this using only the keyboard. Kind regards! Windows Terminal Version: 1.22.12111.0 ### Proposed technical implementation details _No response_
claunia added the Issue-BugNeeds-Tag-FixArea-InteractionProduct-Terminal labels 2026-01-31 08:47:31 +00:00
claunia commented 2026-01-31 08:47:32 +00:00
Author
Owner
Copy Link

@varzenbot commented on GitHub (Sep 17, 2025):

I have found https://github.com/microsoft/terminal/issues/4985 that kind of references what I want, but it seems that the find isn't being taken into account as a possibility.

@varzenbot commented on GitHub (Sep 17, 2025): I have found https://github.com/microsoft/terminal/issues/4985 that kind of references what I want, but it seems that the find isn't being taken into account as a possibility.
claunia commented 2026-01-31 08:47:32 +00:00
Author
Owner
Copy Link

@carlos-zamora commented on GitHub (Oct 1, 2025):

Thanks for filing! A little bit of background. By design, if a selection already exists, when you enter mark mode, you start at that position. So, if you searched for text, the text would be selected, then you could enter mark mode and you'd be exactly where you wanted to be.

It looks like that functionality got changed in #16227 because now search highlights all results, but it doesn't actually select it. We should be able to fix this by starting mark mode at the currently "selected"/found text.

@carlos-zamora commented on GitHub (Oct 1, 2025): Thanks for filing! A little bit of background. By design, if a selection already exists, when you enter mark mode, you start at that position. So, if you searched for text, the text would be selected, then you could enter mark mode and you'd be exactly where you wanted to be. It looks like that functionality got changed in #16227 because now search highlights _all_ results, but it doesn't actually select it. We should be able to fix this by starting mark mode at the currently "selected"/found text.
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-Interaction Issue-Bug Needs-Tag-Fix 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#23623
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?