Skip to content

Scenario: Keyboard Text Selection #4993

Closed

Description

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

Features

Bugs

Misc.

PRs

Activity

  1. ghost added
    Needs-TriageIt's a new issue that the core contributor team needs to triage at the next triage meeting
    on Mar 18, 2020
  2. added
    Area-InputRelated to input processing (key presses, mouse, etc.)
    Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)
    and removed
    Area-InteractionInteracting with the vintage console window (as opposed to driving via API or hooks)
    on Jul 7, 2020
  3. ghost added a commit that references this issue on May 6, 2022
  4. 25 remaining items

  5. added a commit that references this issue on Oct 29, 2023
  6. added a commit that references this issue on Jan 30, 2024
  7. added a commit that references this issue on Apr 14, 2024
  8. added a commit that references this issue on Jun 17, 2024
  9. added a commit that references this issue on Jul 8, 2024
  10. Hermholtz commented on Oct 6, 2024

    @Hermholtz

    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.

  11. added a commit that references this issue on Nov 4, 2025
  12. added a commit that references this issue on Jan 31, 2026
  13. carlos-zamora commented on Mar 13, 2026

    @carlos-zamora
    Author

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Area-InputRelated to input processing (key presses, mouse, etc.)Area-TerminalControlIssues pertaining to the terminal control (input, selection, keybindings, mouse interaction, etc.)Issue-ScenarioNeeds-Tag-FixDoesn't match tag requirementsProduct-TerminalThe new Windows Terminal.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions