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

korean input buffer is not shown (buffer position is wierd) after some commands #13820

Closed
JuhoKang opened this issue Aug 23, 2022 · 4 comments
Closed
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@JuhoKang
Copy link

Windows Terminal version

1.14.1963.0

Windows build number

10.0.22000.856

Other Software

any shell (not because of software)

Steps to reproduce

use some kind of command which has multi line output in shell. I captured some gifs to help you

example 1 (cmd)
cmd

example 2 (ubuntu 20.04)
ubuntu

more info

As I tried to reproduce the problem I found that after the multi line output in shell the buffer position is not matching well.
You can see in example2 the position of buffer is below the view.

Expected Behavior

you can see the korean buffer in the correct position

Actual Behavior

after a multi line output command. the buffer position is wierd

@JuhoKang JuhoKang added the Issue-Bug It either shouldn't be doing this or needs an investigation. label Aug 23, 2022
@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 Aug 23, 2022
@leejy12
Copy link
Contributor

leejy12 commented Aug 23, 2022

I can reproduce this in Terminal version 1.15.2284.0, Windows Build 22622.575.

This occurs when the output overfills(?) the screen buffer and it scrolls down.
See https://streamable.com/30yx6j

Also, it seems that the more the screen scrolls, the greater the position difference

@j4james
Copy link
Collaborator

j4james commented Aug 23, 2022

I think this is probably the same issue as #13769. There's a fix committed which should be available in the next servicing release.

@zadjii-msft
Copy link
Member

Yea, I'm gonna call this a dupe until proven otherwise. Thanks!

/dup #13769

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Aug 23, 2022
@ghost
Copy link

ghost commented Aug 23, 2022

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 Aug 23, 2022
@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 Aug 23, 2022
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Bug It either shouldn't be doing this or needs an investigation. 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

4 participants