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

SHIFT-Curso, CTRL-C and CTRL-V not working but where in old console #3030

Closed
tryptamic opened this issue Oct 2, 2019 · 2 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@tryptamic
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.18362.356] 
Windows Terminal version (if applicable): 0.5.2681.0

# Steps to reproduce

Try to select, copy and paste with the normal windows shortcuts for these operations.

# Expected behavior

I can select, copy and paste text with these shortcuts just like in the old console

# Actual behavior

The operations do not work
@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 Oct 2, 2019
@zadjii-msft
Copy link
Member

This is mostly: /dup #2285 #2749

Additionally, keyboard selection is in spec currently at /dup #2840, with the original issue being /dup #715.

From elsewhere in #2749:

Don't do that, just add a keybinding for copy (that was my bad the action is copy not copyText).

{ "command": "copy", "keys": ["ctrl+c"] },
{ "command": "paste", "keys": ["ctrl+v"] }

should do the trick.

You can set the keybinding to whatever you want. Ctrl+C, Ctrl+Shift+C, Shift+Insert.

@ghost
Copy link

ghost commented Oct 2, 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 Oct 2, 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 Oct 2, 2019
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