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

Un-snapping Terminal Placing Cursor in Middle of Previous Command's Output #7253

Open
joshuacookdev opened this issue Aug 12, 2020 · 4 comments
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Terminal The new Windows Terminal.
Milestone

Comments

@joshuacookdev
Copy link

Environment

Windows build number: 10.0.19041.0
Windows Terminal version (if applicable): 1.1.2021.0

Any other software?
* PowerShell Core 7 (also reproducible in other shells)

Steps to reproduce

  1. Snap terminal to the right
  2. (In PS7) Type a command that fills the screen (I used dotnet new --list because I'm checking my installed templates)
    Step2
  3. Unsnap the pane (whether by dragging, maximizing, or double tapping title bar)
  4. Type new command (I used cd to a path I was working within)

Expected behavior

Terminal should display the new input text at the > mark (seen here in stock PowerShell 7).
expectedBehavior

Actual behavior

Terminal is currently displaying the text in the middle of the previous commands output.
actualBehavior

I searched for snap and cursor and couldn't find this explicitly (I found a couple of related issues) - if duplicated or in progress please feel free to delete.

@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 12, 2020
@joshuacookdev
Copy link
Author

joshuacookdev commented Aug 12, 2020

Looking at it now, it looks like it might be related to #3088 but I don't think it is explicitly the same, since the behavior isn't reproducible in conhost proper.

@zadjii-msft
Copy link
Member

Yea, there's definitely still some sort of intermittent bug with line wrapping. I'm not sure how we get into that state, but it's fairly hard to pin down.

Generally, I'm tracking all these types of bugs over in #5800, so I'll link this report up with those. Thanks!

@zadjii-msft zadjii-msft added Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Terminal The new Windows Terminal. labels Aug 12, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Aug 12, 2020
@zadjii-msft zadjii-msft added this to the Terminal v2.0 milestone Aug 12, 2020
@zadjii-msft zadjii-msft removed the Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting label Aug 12, 2020
@SpiridonovAlexMoeDelo
Copy link

Hi, folks!

Not sure if my issue related to this one but I have next definitely unexpected behavior:
terminal-bug

Requirements:

  1. Terminal have to be full of some text (not reproduced on empty terminal)

What to do:

  1. Get some command from history and try to edit command

What expects:

  1. Just editing without any surprises

What happens:

  1. Suddenly text of command are cloned

100% reproducing as shown on attached gif in very common using scenario.

@zadjii-msft
Copy link
Member

note to self, from #11745:

  • open terminal
  • dotnet new blazorwasm --help
  • maximize

is a 100% repro

@zadjii-msft zadjii-msft modified the milestones: Terminal v2.0, 22H2 Jan 4, 2022
@zadjii-msft zadjii-msft modified the milestones: 22H2, Backlog Jul 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Area-Output Related to output processing (inserting text into buffer, retrieving buffer text, etc.) Issue-Bug It either shouldn't be doing this or needs an investigation. Priority-2 A description (P2) Product-Terminal The new Windows Terminal.
Projects
None yet
Development

No branches or pull requests

3 participants