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

Feature Request: name on tabs #2092

Closed
atyachin opened this issue Jul 25, 2019 · 1 comment
Closed

Feature Request: name on tabs #2092

atyachin opened this issue Jul 25, 2019 · 1 comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@atyachin
Copy link

Summary of the new feature/enhancement

Add the name of the connection/profile on the tabs, specifically useful for remote connections, since currently it's hard to tell which terminal is opened:

image

Proposed technical implementation details (optional)

@atyachin atyachin added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 25, 2019
@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 Jul 25, 2019
@zadjii-msft
Copy link
Member

This is basically the same thing as #608, which was fixed by #1358.

@zadjii-msft zadjii-msft added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jul 25, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 25, 2019
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. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting 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