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

Command Decorations / Marks in the gutter / margin / padding #21134

New Issue
Open
opened 2026-01-31 07:34:09 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 07:34:09 +00:00
Owner
Copy Link

Originally created by @zadjii-msft on GitHub (Jan 24, 2024).

placeholder thread while I actually write something up

Now see, if it was up to me, I'd recommend instead a "icon in the gutter", ala vscode. They've been working on these terminal-driven "quick fixes", that put a lightbulb in the "gutter". That lightbulb is clickable and shows a menu.


Basically, I'm thinking there's a few kinds of things that show up in the gutter:

  • marks for each command, driven by shell integration
  • quick fixes that are driven by some VT escape sequence that we haven't authored yet (so a CLI app could specifically recommend a command)
  • quick fixes that the Terminal generates on a CommandNotFound (<---- what you're working on)
  • quick fixes that are generated based on pattern matching (from that spec)

From Teams:

Trick is, what is the gutter?
We've already got the idea of "padding", but these icons all precipitate the need for like, at least 16px of padding on the left.
Which some people may greatly dislike
But I suppose our DEFAULT_PADDING is "8,8,8,8" already?
Alternatively, the "gutter" could be an "entirely separate thing from the padding". So a user could specifically opt into the gutter, and that would automatically reserve an additional 16px in the left padding.
And that, we could enable already by default (though, it would add left padding for people who already opt'd out)
Regardless. We've got to come up with a clear plan on what to do there first. Then it's easy to just have a VT sequence stick and additional sendInput command into a mark on the gutter, IMO

references

Originally created by @zadjii-msft on GitHub (Jan 24, 2024). placeholder thread while I actually write something up > Now see, if it was up to me, I'd recommend instead a "icon in the gutter", ala vscode. They've been working on these terminal-driven "quick fixes", that put a lightbulb in the "gutter". That lightbulb is clickable and shows a menu. ![](https://user-images.githubusercontent.com/10746682/204557790-d8f924ed-77f7-44a1-80ad-1ade6b83fdaa.png) ![](https://user-images.githubusercontent.com/2193314/204605411-1106e6d4-70ed-4b45-884f-c09dba3cb040.png) ![](https://user-images.githubusercontent.com/29464607/204635771-335ac900-b13a-4a12-8808-36d6ab0f5080.png) Basically, I'm thinking there's a few kinds of things that show up in the gutter: * marks for each command, driven by shell integration * quick fixes that are driven by some VT escape sequence that we haven't authored yet (so a CLI app could specifically recommend a command) * quick fixes that the Terminal generates on a CommandNotFound (<---- what you're working on) * quick fixes that are generated based on pattern matching (from that spec) From Teams: > Trick is, what is the gutter? > We've already got the idea of "padding", but these icons all precipitate the need for like, at least 16px of padding on the left. > Which some people may greatly dislike > But I suppose our DEFAULT_PADDING is "8,8,8,8" already? > Alternatively, the "gutter" could be an "entirely separate thing from the padding". So a user could specifically opt into the gutter, and that would automatically reserve an additional 16px in the left padding. > And that, we could enable already by default (though, it would add left padding for people who already opt'd out) > Regardless. We've got to come up with a clear plan on what to do there first. Then it's easy to just have a VT sequence stick and additional sendInput command into a mark on the gutter, IMO #### references * #15700 * https://github.com/microsoft/vscode/issues/166761 * #16848
claunia added the Issue-TaskIn-PRProduct-TerminalArea-TerminalControl labels 2026-01-31 07:34:09 +00:00
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 In-PR Issue-Task 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#21134
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?