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.

Sign up for GitHub

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

Jump to bottom

Ctrl+A does not select text in WT (in cmd) #10645

Closed
asklar opened this issue Jul 13, 2021 · 6 comments
Closed

Ctrl+A does not select text in WT (in cmd) #10645

asklar opened this issue Jul 13, 2021 · 6 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@asklar
Copy link
Member

asklar commented Jul 13, 2021

Windows Terminal version (or Windows build number)

10.0.22141.0, 1.9.1523.0

Other Software

No response

Steps to reproduce

If you run cmd (using conhost), you can type and then press Ctrl+A to select the whole line
If you run cmd inside Windows Terminal, you get a ^A control code

Expected Behavior

ctrl+A should select the whole line of input

Actual Behavior

Ctrl+A issues a control code ^A
@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 Jul 13, 2021
@asklar
Copy link
Member Author

asklar commented Jul 13, 2021

actually, none of the keyboard selection/navigation shortcuts seem to work: ctrl+shift+left/right arrow don't work either 😔

@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #715 for more discussion.

/dup #715

also see #4993

@ghost
Copy link

ghost commented Jul 13, 2021

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 Jul 13, 2021
@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 Jul 13, 2021
@dxgldotorg
Copy link

Due to leaks about Windows build numbers would it be prudent for OP not to disclose exact build numbers if they are not available to Windows Insiders?

@zadjii-msft
Copy link
Member

Lol I'm not too worried about that - we (normally) work down the hall from @asklar. This isn't something that's particularly impacted by OS version either. He could have put 12.0.0.0 there and it would have been the same thing 😝

@asklar
Copy link
Member Author

asklar commented Jul 14, 2021

I'm on build 0xffff 🙃

@lhecker lhecker mentioned this issue Jun 5, 2023
Open
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@dxgldotorg @zadjii-msft @asklar