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

Terminal looses output when running command that uses progress indicator #14819

Closed
mforkel opened this issue Feb 10, 2023 · 3 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

@mforkel
Copy link

mforkel commented Feb 10, 2023

Windows Terminal version

1.15.3465.0

Windows build number

10.0.19045.2486

Other Software

WSL-Version: 1.0.3.0
WSL distribution: Debian Bullseye

Steps to reproduce

In a tab for the WSL distribtuion, run a command that uses a progress indicator and produces more lines of output than the terminal windows has, e.g. apt-get install php.

Expected Behavior

All lines of output are available when scrolling back up after the command finishes.

Actual Behavior

Most lines of output are lost except for some initial lines (probably not handled be the progress indicator) and the lines shown in the terminal when the command has finished.

The problem does no occur if the option -q (--quiet) is used with apt-get.

@mforkel mforkel added Issue-Bug It either shouldn't be doing this or needs an investigation. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 10, 2023
@j4james
Copy link
Collaborator

j4james commented Feb 11, 2023

What's happening here is that apt-get is setting the scrolling margins (DECSTBM) to keep the progress indicator line fixed, while the top part of the screen scrolls. Unfortunately Windows Terminal doesn't handle that situation very well, so the lines that scroll off the top end up being erased when they should be moved into the scrollback buffer. We're already tracking this problem in issue #3673.

@zadjii-msft
Copy link
Member

/dup #3673

Thanks!

@zadjii-msft zadjii-msft closed this as not planned Won't fix, can't repro, duplicate, stale Feb 13, 2023
@microsoft-github-policy-service
Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 labels Feb 13, 2023
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

3 participants