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

The arrow keys (history) do not work after exiting out a docker container. #5467

Closed
bplasmeijer opened this issue Apr 22, 2020 · 3 comments
Closed
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@bplasmeijer
Copy link

Environment

Windows build number: Microsoft Windows [Version 10.0.18363.752]
Windows Terminal version (if applicable):  0.10.781.0

Any other software? No

Steps to reproduce

Video

1.) open new PowerShell tab
2.) docker run -it mcr.microsoft.com/powershell:lts-alpine-3.10
3.) type 'exit' inside the docker PowerShell container
4.) it will return to the PowerShell terminal

Expected behavior

I can use my arrow keys again, up/down to get the last commands from history.

Actual behavior

The arrow keys don't work, and I need to kill the terminal tab.

Without Windows terminal, the behavior works as expected in a PowerShell window.

@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 Apr 22, 2020
@DHowett-MSFT
Copy link
Contributor

Mercifully, this was just fixed with /dup #4873. The shell in the docker container was leaving the arrow keys in a different mode.

@ghost
Copy link

ghost commented Apr 22, 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 Apr 22, 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 Apr 22, 2020
@bplasmeijer
Copy link
Author

Mercifully, this was just fixed with /dup #4873. The shell in the docker container was leaving the arrow keys in a different mode.

Did test with the new build, works @DHowett-MSFT !

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