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.

Sign up for GitHub

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

Jump to bottom

Don't scroll while backscrolling #5710

Closed
autoantwort opened this issue May 3, 2020 · 5 comments
Closed

Don't scroll while backscrolling #5710

autoantwort opened this issue May 3, 2020 · 5 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting

Comments

@autoantwort
Copy link

Description of the new feature/enhancement

When I backscroll and new output is generated, the terminal should not scroll, otherwise is it nearly impossible to select something.

windows terminal select

Proposed technical implementation details

Here is an example to macOS Terminals does it:

mac terminal
@autoantwort autoantwort added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label May 3, 2020
@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 May 3, 2020
@j4james
Copy link
Collaborator

j4james commented May 3, 2020

I think this is probably covered by issue #980. See also the SnapOnOutput spec in PR #2529.

@autoantwort
Copy link
Author

I think it is a bit different: I do not want scrolling at all when I scroll scroll upwards and new output is generated, like in the macOS terminal. There I can scroll to the top and read the text without selecting anything while new output is generated. This is currently not possible with Windows Terminal

@j4james
Copy link
Collaborator

j4james commented May 3, 2020

Issue #3863 is possibly closer to what you're asking for then. But either way, it's going to need to be part of a more general solution, and that's what the SnapOnOuput spec is meant to be defining.

@autoantwort
Copy link
Author

Yeah this issue is a duplicate of #3863. I want the behavior described in #3863.

@autoantwort
Copy link
Author

Duplicate of #3863

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@j4james @autoantwort