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

Ctrl+Break being treated as Ctrl+C #6874

Closed
wsy opened this issue Jul 11, 2020 · 2 comments
Closed

Ctrl+Break being treated as Ctrl+C #6874

wsy opened this issue Jul 11, 2020 · 2 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@wsy
Copy link

wsy commented Jul 11, 2020

Environment

Windows build number: 10.0.18363.0
Windows Terminal version (if applicable): 1.0.1811.0

Any other software? I tried Windows Powershell, Powershell Core 7.0.1, Cmd.exe

Steps to reproduce

Open Windows Terminal, use "ping" command to ping some address.
Example:

ping -t 192.168.1.1

Then press Ctrl+Break on your keyboard. (I'm using Microsoft Surface Keyboard with FingerprintID, but I assume any full-size keyboard will have the "Pause/Break" key)

Expected behavior

Ping command will receive the Ctrl+Break signal and display statistic info while continuing to send ICMP packages.

Actual behavior

Inside Windows Terminal, "ping" command received Ctrl+C signal instead of Ctrl+Break signal.
I tried this in Powershell Core 7.0.1, Windows Powershell and cmd.exe with legacy conhost.exe, they all handle Ctrl+Break correctly.

image

@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 11, 2020
@zadjii-msft
Copy link
Member

Thanks for the report! Please make sure to search for duplicates when filing new issues. This is already being tracked by another issue on our repo - please refer to #1119 for more discussion.

/dup #1119

This was fixed as a part of #4999, and should be fixed in Terminal Preview 1.1

@ghost
Copy link

ghost commented Jul 13, 2020

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, 2020
@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, 2020
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