-
Notifications
You must be signed in to change notification settings - Fork 9.1k
Closed
Labels
Area-SettingsIssues related to settings and customizability, for console or terminalIssues related to settings and customizability, for console or terminalGathering-DataWe'd like to gather telemetry to influence our decisionWe'd like to gather telemetry to influence our decisionIssue-QuestionFor questions or discussionFor questions or discussionProduct-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.
Description
I've read the other "copy not working" bugs and the universal suggestion seems to be "just create your own keybinding".
It's quite puzzling for a Windows terminal to not come with the most commonly used Windows shortcuts ever.
I'd suggest these two are added to the product, and people can instead change (or remove them) if they wish. I guess that's a much more intuitive default.
For others wondering why they are missing, just add these two to your keybindings:
{ "command": "copy", "keys": ["ctrl+c"] },
{ "command": "paste", "keys": ["ctrl+v"] },
Just to add to the discussion: the built-in Terminal in VS Code supports this out of the box too, which is awesome.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Area-SettingsIssues related to settings and customizability, for console or terminalIssues related to settings and customizability, for console or terminalGathering-DataWe'd like to gather telemetry to influence our decisionWe'd like to gather telemetry to influence our decisionIssue-QuestionFor questions or discussionFor questions or discussionProduct-TerminalThe new Windows Terminal.The new Windows Terminal.Resolution-Fix-CommittedFix is checked in, but it might be 3-4 weeks until a release.Fix is checked in, but it might be 3-4 weeks until a release.