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

Scenario: Keyboard Text Selection #6968

New Issue
Open
opened 2026-01-31 00:51:51 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 00:51:51 +00:00
Owner
Copy Link

Originally created by @carlos-zamora on GitHub (Mar 18, 2020).

Originally assigned to: @carlos-zamora on GitHub.

[Original issue: #715] [Original Spec: #2840] [Mark mode spec: #5804] [initial PR: #10824] [markers PR: #10865]

Features

Bugs

Misc.

  • Remove optional param for copy func, manually clear selection instead
  • feedback from #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

Originally created by @carlos-zamora on GitHub (Mar 18, 2020). Originally assigned to: @carlos-zamora on GitHub. ##### [Original issue: #715] [Original Spec: #2840] [Mark mode spec: #5804] [initial PR: #10824] [markers PR: #10865] ## Features * [x] #715 * [x] Quick Edit (modify existing selection w/ keyboard) * [x] #1469 * implicit mark mode * [ ] #11985 - see also: #13369 * [x] [follow-up] #3663 * [x] [follow-up] #6649 * [x] [follow-up] #4985 ## Bugs - #13413 - #13447 - #13485 ## Misc. * [ ] [Remove optional param for copy func, manually clear selection instead](https://github.com/microsoft/terminal/pull/13360#discussion_r905290481) * feedback from #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... - #2840 - #5804 - Impl... - #3758 - #10824 - #13045 - #10865 - #13053 - #13358 - #13370 - #13405 - #13435
claunia added the Area-InputProduct-TerminalArea-TerminalControlIssue-Scenario labels 2026-01-31 00:51:51 +00:00
claunia commented 2026-01-31 00:51:52 +00:00
Author
Owner
Copy Link

@Hermholtz commented on GitHub (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.:

  • Selection with SHIFT+arrows, SHIFT+CTRL+arrows, SHIFT+Home, End.
  • Cut, Copy, Paste using familiar keys.
  • The entire selected text is overwritten when I press a "normal" key, e.g. a letter, a symbol or a digit, or when I paste something.
  • The selection is cleared when I press navigation key (arrow, CTRL+arrow, Home, End, PgUp, PgDn).

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.

@Hermholtz commented on GitHub (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.: - Selection with SHIFT+arrows, SHIFT+CTRL+arrows, SHIFT+Home, End. - Cut, Copy, Paste using familiar keys. - The entire selected text is overwritten when I press a "normal" key, e.g. a letter, a symbol or a digit, or when I paste something. - The selection is cleared when I press navigation key (arrow, CTRL+arrow, Home, End, PgUp, PgDn). 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.
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-Input Area-TerminalControl Issue-Scenario 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#6968
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?