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: report errors that occur when starting a new tab #2745

Closed
pcolmer opened this issue Sep 13, 2019 · 2 comments
Closed

Feature Request: report errors that occur when starting a new tab #2745

pcolmer opened this issue Sep 13, 2019 · 2 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

@pcolmer
Copy link

pcolmer commented Sep 13, 2019

Description of the new feature/enhancement

When launching a new tab, if any error occurs during the startup of the tab (e.g. an error from the command being run), Terminal needs to display the error rather than just close the tab.

This would help the user to better understand why the tab hasn't successfully opened.

An example of where this is useful is SSH terminal connections. The ssh command can fail for a number of reasons, e.g. ssh-agent isn't running, connection to server timed out, etc. At the moment, Terminal just closes the newly opened tab without any explanation.

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

I'm pretty sure this is related to:

/dupe #1364 #2039 #2091 #982 #2563

I'm resolving it as a dupe of that collection of issues.

@DHowett-MSFT Is there a master issue for all those? They all seem very closely related, but there's no master "Add graceful closeOnExit setting, and display errors on ungraceful exits" issue

@ghost
Copy link

ghost commented Sep 13, 2019

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 Sep 13, 2019
@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 Sep 13, 2019
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