Something like "unfocusedAppearance" but for when the process is dead / no longer running + reportCommandStart option #18489
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.
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: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 theirprofile.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 totrue
... would immediately echo a line likeRunning: ${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 toRunning:
The text was updated successfully, but these errors were encountered: