Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug Report (Windows PowerShell CTRL+C no longer works for copying selected text) #2749

Closed
JeremyTBradshaw opened this issue Sep 13, 2019 · 3 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@JeremyTBradshaw
Copy link

Environment

Windows build number: Microsoft Windows NT 10.0.18362.0
Windows Terminal version (if applicable): Version: 0.4.2382.0

Any other software?

Steps to reproduce

  1. Highlight text in Windows PowerShell, in Windows Terminal.
  2. Press CTRL+C and watch as a new line is generated but realize the selected text is both no longer selected and not on the clipboard.

Expected behavior

CTRL+C should continue to work for copying text out of Windows PowerShell.

Actual behavior

CTRL+C is instead just the typical cancel and new line.

@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 13, 2019
@DHowett-MSFT
Copy link
Contributor

Hey, thanks for the report! This’ll be the same as /dup #2285. Your key bindings are configurable, and if you bind ctrl+c as copy you’ll get the behavior you’re expecting.

@ghost
Copy link

ghost commented Sep 13, 2019

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost ghost closed this as completed Sep 13, 2019
@ghost ghost added Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. and removed Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Sep 13, 2019
@JeremyTBradshaw
Copy link
Author

@DHowett-MSFT Thanks and awesome. I searched for "ctrl copy" and a few other trying-to-be-smart searches, but didn't see that issue. Glad it is such an easy solution.

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Development

No branches or pull requests

2 participants