-
Notifications
You must be signed in to change notification settings - Fork 29.3k
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
Sticky scroll for terminal commands #172742
Comments
This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
🙁 In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation. Happy Coding! |
Put together a WIP prototype for this: Branch: https://github.com/microsoft/vscode/tree/tyriar/172742_sticky_scroll |
Can I give it a try. |
@tisilent this one would be best done by me imo as it needs some iterating within the team and with ux designers |
Quoting @lunasorcery:
This would bring VSCode's existing sticky scroll support to terminals for easier viewing and editing of commands with long outputs.
Suggested implementation
Use shell integration to track commands and render the currently scrolled output's command at the top of the editor in a sticky scroll if it doesn't fit on the screen.
Potential problems
If a command's output is larger than the terminal's buffer, its command may no longer exist. We may need to cache the last command if it's not already accessible by the shell integration.
Prior art
The text was updated successfully, but these errors were encountered: