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

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

Closed
hi2u opened this issue Feb 1, 2025 · 3 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

@hi2u
Copy link

hi2u commented 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:

@hi2u hi2u added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Feb 1, 2025
@microsoft-github-policy-service microsoft-github-policy-service bot added Needs-Tag-Fix Doesn't match tag requirements Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Feb 1, 2025
@carlos-zamora
Copy link
Member

Thanks for filing! This is related to several other issues (i.e. #11111) where users want customizations for different states of the Terminal. A consistent problem we've been running into is that we need a way to resolve combined states (i.e. admin session that is unfocused).

We're going to mark this as a /duplicate of #17780 as we're tracking the idea of customizing sessions that are terminated there.

Copy link
Contributor

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!

@microsoft-github-policy-service microsoft-github-policy-service bot 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 Feb 5, 2025
@hi2u
Copy link
Author

hi2u commented Feb 6, 2025

@carlos-zamora thanks, yeah I can understand the multiplier factor complicating things.

I've written a comment here with my idea for that.

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