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

Using Microsoft Telnet in Windows Terminal display and inputs bug #7689

Closed
rhdlilj opened this issue Sep 21, 2020 · 2 comments
Closed

Using Microsoft Telnet in Windows Terminal display and inputs bug #7689

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

Comments

@rhdlilj
Copy link

rhdlilj commented Sep 21, 2020

Environment

Windows build number: 10.0.18363.1082
Windows Terminal version (if applicable):1.2.2381.0

Microsoft Telnet

Steps to reproduce

  1. Using Microsoft Telnet in Windows Terminal, if the output lines more then the window size, the scroll bcak context display is wrong。
    image

  2. And then, if changing the window size smaller, input will be failed too.
    image

Expected behavior

1.the scroll bcak context display shuld be correct.
2.input shuld be ok.

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

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

/dup #6056

@ghost
Copy link

ghost commented Sep 21, 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 Sep 21, 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 Sep 21, 2020
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
2 participants
@zadjii-msft @rhdlilj