starred/terminal
1
0
Fork 0
mirror of https://github.com/microsoft/terminal.git synced 2026-02-04 05:35:20 +00:00
Code Issues 19.0k Packages Projects Releases 20 Wiki Activity

Vscode-style sticky-scrolling but with prompts #19280

New Issue
Open
opened 2026-01-31 06:38:55 +00:00 by claunia · 1 comment
claunia commented 2026-01-31 06:38:55 +00:00
Owner
Copy Link

Originally created by @Mrkol on GitHub (Jan 30, 2023).

Description of the new feature/enhancement

Original idea by @lunasorcery, approved by @DHowett
https://twitter.com/DHowett/status/1619856783119626242
You know how vscode is able to "stick" the namespace/class name or function signature to the top of the screen when some part of the relevant code scope is "above" the viewport? That, but for commands that output a bunch of data, with the original prompt/command being sticky.
This should increase the productivity in exactly the same manner as the feature does inside vscode: easier to browse large histories with commands outputting a bunch of stuff.
It could also be convenient to make the sticky part clickable to scroll up to the beginning of the command output.

Proposed technical implementation details (optional)

Originally created by @Mrkol on GitHub (Jan 30, 2023). <!-- 🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨 I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING: 1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement. 2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement. 3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number). 4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement. 5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement. All good? Then proceed! --> # Description of the new feature/enhancement Original idea by [@lunasorcery](https://twitter.com/lunasorcery), approved by @DHowett https://twitter.com/DHowett/status/1619856783119626242 You know how vscode is able to "stick" the namespace/class name or function signature to the top of the screen when some part of the relevant code scope is "above" the viewport? That, but for commands that output a bunch of data, with the original prompt/command being sticky. This should increase the productivity in exactly the same manner as the feature does inside vscode: easier to browse large histories with commands outputting a bunch of stuff. It could also be convenient to make the sticky part clickable to scroll up to the beginning of the command output. <!-- A clear and concise description of what the problem is that the new feature would solve. Describe why and how a user would use this new functionality (if applicable). --> # Proposed technical implementation details (optional) <!-- A clear and concise description of what you want to happen. -->
claunia added the Issue-FeatureProduct-TerminalArea-TerminalControl labels 2026-01-31 06:38:55 +00:00
claunia commented 2026-01-31 06:38:55 +00:00
Author
Owner
Copy Link

@zadjii-msft commented on GitHub (Jan 30, 2023):

yes

It could also be convenient to make the sticky part clickable to scroll up to the beginning of the command output

absolutely yes

We need to figure out what we want the UX of this to look like exactly, but I love it. I'll link it up.

aside: Do we want it to have the commandline? or maybe the directory? Toggle between the two? Nah, directory seemed like something that was a good idea at 3am but I already don't think it's a great idea.

@zadjii-msft commented on GitHub (Jan 30, 2023): _yes_ > It could also be convenient to make the sticky part clickable to scroll up to the beginning of the command output _absolutely yes_ We need to figure out what we want the UX of this to look like exactly, but I love it. I'll link it up. _aside_: Do we want it to have the commandline? or maybe the directory? Toggle between the two? Nah, directory seemed like something that was a good idea at 3am but I already don't think it's a great idea.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
⛺ Reserved
A11yCO
A11yMAS
A11ySev1
A11ySev2
A11ySev3
A11yTTValidated
A11yUsable
A11yVoiceAccess
A11yWCAG
Area-Accessibility
Area-AtlasEngine
Area-AzureShell
Area-Build
Area-Build
Area-Chat
Area-CmdPal
Area-CodeHealth
Area-Commandline
Area-CookedRead
Area-DefApp
Area-Extensibility
Area-Fonts
Area-GroupPolicy
Area-i18n
Area-Input
Area-Interaction
Area-Interop
Area-Localization
Area-Output
Area-Performance
Area-Portable
Area-Quality
Area-Remoting
Area-Rendering
Area-Schema
Area-Server
Area-Settings
Area-SettingsUI
Area-ShellExtension
Area-ShellExtension
Area-ShellExtension
Area-Suggestions
Area-Suggestions
Area-TerminalConnection
Area-TerminalControl
Area-Theming
Area-UserInterface
Area-VT
Area-Windowing
Area-WPFControl
AutoMerge
Blocking-Ingestion
Culprit-Centennial
Culprit-WinUI
Disability-All
Disability-Blind
Disability-LowVision
Disability-Mobility
External-Blocked-WinUI3
Fixed
Gathering-Data
good first issue
HCL-E+D
HCL-WindowsTerminal
Help Wanted
Impact-Compatibility
Impact-Compliance
Impact-Correctness
Impact-Visual
In-PR
InclusionBacklog
InclusionBacklog-Windows TerminalWin32
InclusionCommitted-202206
Issue-Bug
Issue-Docs
Issue-Feature
Issue-Feature
Issue-Question
Issue-Samples
Issue-Scenario
Issue-Task
Needs-Attention
Needs-Author-Feedback
Needs-Bisect
Needs-Discussion
Needs-Repro
Needs-Tag-Fix
Needs-Tag-Fix
Needs-Triage
No-Recent-Activity
Priority-0
Priority-1
Priority-2
Priority-3
Product-Cmd.exe
Product-Colortool
Product-Colortool
Product-Colortool
Product-Conhost
Product-Conpty
Product-Meta
Product-Powershell
Product-Terminal
Product-WSL
pull-request
Mirrored from GitHub Pull Request
 Resolution-Answered
Resolution-By-Design
Resolution-Duplicate
Resolution-External
Resolution-Fix-Available
Resolution-Fix-Committed
Resolution-No-Repro
Resolution-Won't-Fix
Severity-Blocking
Severity-Crash
Severity-DataLoss
spam
this-will-be-a-breaking-change
Tracking-External
WindowsTerminal_Win32
Work-Item
zAskModeBug
zInbox-Bug
No Label Area-TerminalControl Issue-Feature Product-Terminal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
claunia
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#19280
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?