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

Include active sub process in tab title. #5137

Closed
cpietrzykowski opened this issue Mar 26, 2020 · 3 comments
Closed

Include active sub process in tab title. #5137

cpietrzykowski opened this issue Mar 26, 2020 · 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

@cpietrzykowski
Copy link

Description of the new feature/enhancement

With cmd.exe (for example) the title of the window includes the active process (when it differs from the shell). This would be welcome for Windows Terminal, most notably when there are multiple active tabs per host.

Proposed technical implementation details (optional)

Either append the process name to the tab title, or provide some profile customisation formats to give the user some control over what/when the tab title is automatically updated to reflect shell activity.

When a non-trivial sub process is started (say if the task takes longer than a few hundred millseconds), append the process name to the tab title.

Some shells support dynamic prompts, but I don't think they're all consistent with how events are triggered. (understanding that not all processes would be visible to the host -- i.e. Powershell -> ssh -> vi; would only result in the tab title being "ssh".)

I'd be happy to take a stab at implementing this if a more seasoned maintainer could point me in the right direction.

@cpietrzykowski cpietrzykowski added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Mar 26, 2020
@ghost ghost added 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 Mar 26, 2020
@DHowett-MSFT
Copy link
Contributor

Thanks for the request! I'd like for it to be part of the spec for #1320 -- we'll need to have a discussion about what we can do with our subprocess' token, and what makes sense to scrape to put in the title.

Mind moving future discussion for this feature over there?

Thanks!

/dup #1320

@ghost
Copy link

ghost commented Mar 27, 2020

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!

@ghost ghost closed this as completed Mar 27, 2020
@ghost ghost 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 Mar 27, 2020
@cpietrzykowski
Copy link
Author

Thanks for the request! I'd like for it to be part of the spec for #1320 -- we'll need to have a discussion about what we can do with our subprocess' token, and what makes sense to scrape to put in the title.

Mind moving future discussion for this feature over there?

Thanks!

/dup #1320

No problem at all -- I assure you I searched countless times looking for a dupe, trying all manner of search terms.

This issue was closed.
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