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

scrolling in emacs scrolls the screen, not emacs buffer #9545

Closed
tsengalb99 opened this issue Mar 19, 2021 · 11 comments
Closed

scrolling in emacs scrolls the screen, not emacs buffer #9545

tsengalb99 opened this issue Mar 19, 2021 · 11 comments
Labels
Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@tsengalb99
Copy link

In linux terminals (gnome terminal, konsole, termux, etc.), scrolling in an emacs window moves the cursor, not the actual output. Currently (version 1.6.10571.0), scroll behavior in Windows Terminal appears to be captured by the terminal and not passed on to the application, as it should. I am almost certain this is an issue with Terminal since MinTTY handles scrolling fine with GitBash, but Terminal does not.

Will this be fixed (when I last used windows terminal half a year ago, I noticed this problem), and if so, when?

@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 Mar 19, 2021
@skyline75489
Copy link
Collaborator

what version of emacs are you using? Are you using WSL? Are you using SSH?

@skyline75489
Copy link
Collaborator

It's a bit complicated, but although MinTTY (GitBash) looks like Terminal, the underlying tech stacks are very different.

@tsengalb99
Copy link
Author

ssh to an ubuntu machine, emacs 25.2.2, but the version of emacs does not seem to make a difference (tried this on multiple machines)

@skyline75489
Copy link
Collaborator

OK that makes sense. I know it sounds easy, there's actually a lot of things that need to be fixed, OpenSSH on Windows being an example. See #8528 (comment) .

You can try the newer version of OpenSSH in Win32-OpenSSH repo.

@tsengalb99
Copy link
Author

I installed the newer version of openssh, but the cursor still doesn't scroll. The screen stops scrolling, which is nice, but the cursor is still stuck.

@tsengalb99
Copy link
Author

tsengalb99 commented Mar 19, 2021

Also, it doesnt completely make sense to me why openssh on windows would be the issue. Git Bash ships with its own version of ssh (presumably also openssh), which works fine in mintty but not windows terminal. Doesn't this imply terminal's handling of scrolling and ssh is wonky? Mintty seems to handle it just fine.

@skyline75489
Copy link
Collaborator

You see, the MinTTY (together with its openssh) runs inside MSYS, which is kind of a minimal Linux environment on Windows. But the Win32-OpenSSH you're using is a native version of OpenSSH running on Windows. These two versions of OpenSSH are mostly the same, but remarkably different about how they interact with terminals. That's why you may find the SSH shipped with Git Bash is not working inside Windows Terminal. I don't want to bore you with all the technical details. The conclusion is that, the entire terminal ecosystem on Windows is not (yet) as complete as Linux. MSYS was the "old" solution that simulate what Linux does on Windows. Windows Terminal is the new kid in town.

@tsengalb99
Copy link
Author

Interesting. How would I go about getting functioning scroll behavior then? It appears that the latest openssh still doesn't handle scrolling correctly.

I would use mintty except it doesn't offer tabs, and the other features of windows terminal are useful too.

@skyline75489
Copy link
Collaborator

skyline75489 commented Mar 19, 2021

I wish I could help but I'm a Vim user. And I don't know the SSH side of the story that well. Please be patient and wait for the response from the core developers of this project.

I know it sounds a simple issue that should be solved a long time ago. But trust me, most what you see is just the tip of an iceberg. Take a look at the 1200+ issues in this repo and you'll know what I mean. As a terminal project, Windows Terminal is actually very young (six years old roughly?), comparing to GNOME terminals and alike, which is like 20+ years old. And Windows is fundamentally different than *nix in so many ways. So please keep calm & have a little patience 😃

@zadjii-msft
Copy link
Member

This sounds a lot like #9534. I think at the end of the day, this is caused by the Terminal not properly supporting the alternate screen buffer.

/dup #381
/dup #3321

@ghost
Copy link

ghost commented Mar 19, 2021

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 Mar 19, 2021
@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 Mar 19, 2021
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

3 participants