Repository navigation
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.
Reacted by Claire Novotny, Nate McMaster, Nicolas Luque, Daniel Cazzulino, Muhammad Azeez, Kirill Osenkov, Sergey Mirvoda, Diego Vega, Marko Lahma, James Croft and 29 more
Reacted by Brad Wilson, Sebastián Monía, Kip Obenauf, Zach Bean, Karol Piłat, Tatsunori Uchino, Pavel Šmejkal, Marcus Schweda, Stewart Stewart, Jingbei Li and 2 more
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.
Activity
KirillOsenkov commentedon Oct 4, 2019
cmd.exe didn't support these for years and finally added them quite recently. Even more puzzling to have these missing in the new one.
ealsur commentedon Oct 4, 2019
Copy and Paste was added in 0.3, if you installed 0.3 (or later), they were there by default. If you upgraded to 0.3, you needed to add them manually: https://devblogs.microsoft.com/commandline/windows-terminal-preview-v0-3-release/
pedroreys commentedon Oct 4, 2019
For the curious, here is the PR where they added the default keybindings for copy and paste and they discuss the challenges of using
Ctrl+Cby default.There is also #2285 that has extensive discussion about using Ctrl+C for copy vs emitting SIGINT.
bradwilson commentedon Oct 4, 2019
Please don't do this. Ctrl+C already has meaning inside terminals that long outdates copy/paste.
DHowett-MSFT commentedon Oct 4, 2019
This is a delightful vignette about why we have rebindable key actions, and why we don't want to be prescriptive with user experience where "terminal input" is concerned.
DHowett-MSFT commentedon Oct 7, 2019
We can 100% bind Ctrl+C by default, now that we have support for passing through bindings that didn't trigger an action. We can 100% not bind Ctrl+V by default.
KirillOsenkov commentedon Oct 8, 2019
I know
Ctrl+Ccancels the current execution, but what doesCtrl+Vdo? Out of curiosity.bradwilson commentedon Oct 8, 2019
Kirill Osenkov (@KirillOsenkov) https://superuser.com/a/421468
sgreenmsft commentedon Oct 10, 2019
My (admittedly uneducated) guess is the percentage of users expecting Ctrl+V to result in paste is substantially larger than the percentage of users expecting Ctrl+V to result in "verbatim insert mode."
17 remaining items
Update default settings.json experience (#5217)
vadimkantorov commentedon Apr 27, 2020
Given that "Ctrl+C" is now default copy keybinding on new installations. how will standard "Ctrl+C" for SIGINT work?
Imagine a long-running console program with some text selected and Ctrl+C typed. What will Windows Terminal do? Copy? Interrupt the program? Both? Carlos Zamora (@carlos-zamora)
zadjii-msft commentedon Apr 27, 2020
If the user doesn't like that behavior, it's pretty trivial to remove the new Ctrl+c binding from their
settings.json, and rely on the Ctrl+shift+c binding that's indefaults.jsonrandomascii commentedon Apr 27, 2020
Does Enter now copy text by default? I realized when switching from cmd.exe to the new terminal that I use that to copy text a lot. I'm not sure if there is any significant disadvantage to making that the default, and it seems that the new terminal should, where possible, ease the transition from cmd.exe.
zadjii-msft commentedon Apr 27, 2020
Bruce Dawson (@randomascii) nope, but that is a lot less common of a scenario for our users then Ctrl+C for copy. There's a balance we need to strike between "keeping the old behavior of conhost" and "making space to create a better experience". For those of our users who actually do want copy on enter, adding it isn't terribly difficult:
{ "command": "copy", "keys": ["enter"] },but I'd bet most people weren't even aware that feature existed in the original conhost 😆
rbreaves commentedon May 31, 2020
Garrett D'Amore (@gdamore) What you’ve suggested is actually the most practical thing in this thread. Checkout my https://github.com/rbreaves/kinto project.
Daniel Cazzulino (@kzu)
stewSquared commentedon Jun 27, 2020
Okay great. Now how do we disable this?
-- sad linux user
Edit: Nevermind. Found it in settings.json and deleted it.
installwindows commentedon Aug 5, 2020
Coming from Linux, it was confusing to ctrl-v in vim and see my last pasta. Had to google on how to get the standard behavior.
churchid commentedon Sep 24, 2020
The problem with a terminal application commandeering these shortcuts is that when you run applications inside of the terminal and find yourself with a need to enter that key combination inside the terminal, your SOL. Registered voter against the new default, but I guess the change is in, so will go delete it.
stewSquared commentedon Sep 24, 2020
The fact people think this keybinding is obscure demonstrates ignorance. I recommend learning to use the standard keybindings before bashing them. (heh)
What ctrl+v does depends on what terminal application is running. For people who use terminals on a daily basis, this usually means "page down" for pagers and editors (reading a man page, emacs, vim). alt-v is usually page up. Counter to your intuition, this is quite frequently used.
At this point, why not steal the keybindings for ctrl-a, ctrl-t, and crtl-w, since windows users expect them to be select all, new tab, and close tab? The fact is, these are also very useful keybindings in terminal applications. We should encourage people to leave their comfort zone and learn the terminal, instead of defaulting to a Frankenstein with inconsistent exceptions.