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

Something like "unfocusedAppearance" but for when the process is dead / no longer running + reportCommandStart option #22828

New Issue
Open
opened 2026-01-31 08:24:41 +00:00 by claunia · 0 comments
claunia commented 2026-01-31 08:24:41 +00:00
Owner
Copy Link

Originally created by @hi2u on GitHub (Feb 1, 2025).

Prior work: unfocusedAppearance

I really love the unfocusedAppearance override that lets us set different styling for windows that aren't focused. Really useful when you have lots of monitors. This feature alone means I have little interest in switching to any other alternative terminal program that didn't have this.

Same as above, but for: process running state

I also use the closeOnExit: "never" setting in most of my profiles, which means that my terminal windows can be either in:

  • State A) The normal running state
  • State B) Between executions, i.e. when I'm still sitting at the prompt below (and haven't hit Enter yet):
[process exited with code 0 (0x00000000)]
You can now close this terminal with Ctrl+D, or press Enter to restart.

It would be awesome if a clone of same styling override object like unfocusedAppearance could also be defined for state B above, so it's super obvious at a glance which terminals aren't actually running their profile.commandline process right now.

It could be named deadProcessAppearance or something like that.

It would be especially handy when your process has a long startup time, i.e. you've hit Enter to restart it, but maybe it hasn't displayed anything yet, or it just doesn't do a lot of output in general. I find that for these types of processes, I'm often sitting here wondering if I did actually hit Enter yet (or pressed it too softly, or another window was focused etc), so I end up mashing the Enter key like 3 times to be sure, haha.

Bonus idea: reportCommandStart

Additionally, related to these types of use cases:

It would also be nice if there were a boolean toggle setting per-profile called something like reportCommandStart?: boolean, where if set to true... would immediately echo a line like Running: ${profile.commandline} as soon as I hit Enter.

Or better yet, make the option a string such as: reportCommandStartPrefix?: string so you can specify your own alternative to Running:

Originally created by @hi2u on GitHub (Feb 1, 2025). ### Prior work: `unfocusedAppearance` I really love the [`unfocusedAppearance`](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/profile-appearance#unfocused-appearance-settings) override that lets us set different styling for windows that aren't focused. Really useful when you have lots of monitors. This feature alone means I have little interest in switching to any other alternative terminal program that didn't have this. ### Same as above, but for: process running state I also use the [`closeOnExit: "never"`](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/profile-advanced#profile-termination-behavior) setting in most of my profiles, which means that my terminal windows can be either in: * State A) The normal running state * State B) Between executions, i.e. when I'm still sitting at the prompt below (and haven't hit Enter yet): ``` [process exited with code 0 (0x00000000)] You can now close this terminal with Ctrl+D, or press Enter to restart. ``` It would be awesome if a clone of same styling override object like [`unfocusedAppearance`](https://learn.microsoft.com/en-us/windows/terminal/customize-settings/profile-appearance#unfocused-appearance-settings) could also be defined for state B above, so it's super obvious at a glance which terminals aren't actually running their `profile.commandline` process right now. It could be named `deadProcessAppearance` or something like that. It would be especially handy when your process has a long startup time, i.e. you've hit Enter to restart it, but maybe it hasn't displayed anything yet, or it just doesn't do a lot of output in general. I find that for these types of processes, I'm often sitting here wondering if I did actually hit Enter yet (or pressed it too softly, or another window was focused etc), so I end up mashing the Enter key like 3 times to be sure, haha. ### Bonus idea: `reportCommandStart` Additionally, related to these types of use cases: It would also be nice if there were a boolean toggle setting per-profile called something like `reportCommandStart?: boolean`, where if set to `true`... would immediately echo a line like `Running: ${profile.commandline}` as soon as I hit Enter. Or better yet, make the option a string such as: `reportCommandStartPrefix?: string` so you can specify your own alternative to `Running: `
claunia added the Issue-FeatureResolution-Duplicate labels 2026-01-31 08:24:41 +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 Issue-Feature Resolution-Duplicate
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#22828
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?