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

Scrollback buffer doesn't work with screen #5284

Closed
wmertens opened this issue Apr 8, 2020 · 2 comments
Closed

Scrollback buffer doesn't work with screen #5284

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

Comments

@wmertens
Copy link

wmertens commented Apr 8, 2020

Environment

Windows build number: 10.0.19041.172
Windows Terminal version (if applicable): 0.10.781.0

Any other software? GNU screen in WSL2

Steps to reproduce

I have the following in my .screenrc:

  termcapinfo xterm*|xs ti=\E7\E[?47l

This makes it so screen doesn't internally scroll but instead just lets lines go out into the terminal, so that I can scroll the terminal buffer which is bigger and faster than screen's buffer.

Expected behavior

This setting works in all terminals I've used so far, including Hyper

Actual behavior

In Terminal, the setting has no effect, and the screen scrollback buffer doesn't flow into the terminal scrollback buffer.

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

This is the intersection of a couple different issues.

/dup #3082 #3673

Thanks!

@ghost
Copy link

ghost commented Apr 10, 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 10, 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 10, 2020
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