Repository navigation
Closed
Labels
Area-InputRelated to input processing (key presses, mouse, etc.)Related to input processing (key presses, mouse, etc.)Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Issue-ScenarioNeeds-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.The new Windows Terminal.
Milestone
Description
[Original issue: #715] [Original Spec: #2840] [Mark mode spec: #5804] [initial PR: #10824] [markers PR: #10865]
Features
- Terminal: Support keyboard text selection & navigation #715
- Quick Edit (modify existing selection w/ keyboard)
- Ability to select/copy all the text in the session #1469
- implicit mark mode
- [follow-up] Mark Mode: Toggle instead of holding shift #3663
- [follow-up] Keyboard navigation of clickable link #6649
- [follow-up] Moving the cursor when scrolling in the history to select text #4985
Bugs
- [1.15] switchSelectionEndpoint doesn't work #13413
- A11y: windows terminal emits selection/deselection events in mark mode when navigating with arrow keys #13447
- select all marker visibility #13485
Misc.
- Remove optional param for copy func, manually clear selection instead
- feedback from Mark Mode should preempt key bindings, and work with anything that causes scrolling... #13533:
- Prioritize mark mode key bindings over custom key bindings when in mark mode
- Scrolling...
- [PROTOTYPE] scrolling should move the "mark"
- If we've scrolled, then we enter mark mode, start position should be somewhere in the visible area (NOT back at the input buffer aka the cursor position).
PRs
- Spec...
- Impl...
- Implement keybindings to quick edit selection #3758
- Implement Keyboard Selection #10824
- Add ability to select all text in the buffer #13045
- Add selection marker overlays for keyboard selection #10865
- Introduce Mark Mode #13053
- Miscellaneous bug fixes for Mark Mode #13358
- Introduce
switchSelectionEndpointaction #13370 - Add keyboard navigation to hyperlinks #13405
- Update renderer on
SwitchSelectionEndpoint#13435
Reacted by NN, Simone Perriello, Sebastian Brandt, Max Levitskiy, Lucas Silva, Bartosz Popiela, Matthew A Cargile, ClauS, Mo and Alex Angas
Metadata
Metadata
Assignees
Labels
Area-InputRelated to input processing (key presses, mouse, etc.)Related to input processing (key presses, mouse, etc.)Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Issues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Issue-ScenarioNeeds-Tag-FixDoesn't match tag requirementsDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.The new Windows Terminal.
Activity
Add ability to select all text in the buffer (#13045)
25 remaining items
[ImgBot] Optimize images
[ImgBot] Optimize images
[ImgBot] Optimize images
[ImgBot] Optimize images
[ImgBot] Optimize images
[ImgBot] Optimize images
[ImgBot] Optimize images
Hermholtz commentedon Oct 6, 2024
I would like to be able to edit text in Windows Terminal the same way it happens e.g. in Notepad, Microsoft Word or all other applications, i.e.:
The Mark Mode is interesting, but not really what Microsoft made us familiar with since '90s. It maybe has its users, but the majority learned to work the way I described above. Mark mode reminds me of the WordStar editor from '80s where CTRL+K, B marked the beginning of a block, and CTRL+K, K marked the end, and then it was persisting until you did some operation on it. It was interesting (seemed quite standard and useful at that time), but Microsoft got us used to a volatile selection and its way of working with it.
Please then bring the Microsoft way of working with selections to Microsoft Windows Terminal.
Thank you.
[ImgBot] Optimize images
[ImgBot] Optimize images
[ImgBot] Optimize images
[ImgBot] Optimize images
carlos-zamora commentedon Mar 13, 2026
Closing this issue. All of the referenced issues except for #11985 are resolved, and even then, #11985 can be worked around my entering mark mode with ctrl+shift+M.
For any other issues related to keyboard selection, please file a new issue on the repo.