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

Scroll Lock button support to lock the terminal from scrolling #6694

Closed
lcsondes opened this issue Jun 26, 2020 · 2 comments
Closed

Scroll Lock button support to lock the terminal from scrolling #6694

lcsondes opened this issue Jun 26, 2020 · 2 comments
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@lcsondes
Copy link

Description of the new feature/enhancement

Support Scroll Lock to lock text from scrolling if I want to look at something that was briefly visible but is now off screen because there's a constant stream of new output from, e.g., compiling or watching some logs live with tail.

Proposed technical implementation details (optional)

If I have Scroll Lock on, new output arriving into the terminal should not scroll it down so I can keep reading what's currently visible on screen. Having Scroll Lock off would restore the behavior that's the only one as of writing.

@lcsondes lcsondes added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 26, 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 Jun 26, 2020
@DHowett
Copy link
Member

DHowett commented Jun 26, 2020

I agree. We've got a couple specs in flight here (#2529, for #980), and #3863 mentions scroll lock. Once we have keyboard selection (#2840 spec), that'll include keyboard buffer navigation, and we can extend #2529 to cover scroll lock as well. We're also considering "mark" mode (a mode you switch into where you can navigate the buffer solely by keyboard)

/dup #3863, #715

@ghost
Copy link

ghost commented Jun 26, 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 Jun 26, 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 Jun 26, 2020
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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