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.

Sign up for GitHub

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

Jump to bottom

Allow a "no tabs open" state #10987

Closed
Convincible opened this issue Aug 19, 2021 · 2 comments
Closed

Allow a "no tabs open" state #10987

Convincible opened this issue Aug 19, 2021 · 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

@Convincible
Copy link

Description of the new feature/enhancement

  1. Allow me to close ALL tabs while keeping Terminal open as a program.
  2. Allow this to be the default state for the app.
  3. On the "no tab open" screen, offer large buttons to launch a particular terminal.

This would improve usability for users who want to use Windows Terminal but need to use a different terminal each time. Some days I need to launch Ubuntu constantly. Other days it's PowerShell. It's annoying to always launch with a particular terminal, then load another one, then close the first one.

Proposed technical implementation details (optional)
@Convincible Convincible added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Aug 19, 2021
@ghost ghost 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 Aug 19, 2021
@zadjii-msft
Copy link
Member

Thanks for the suggestion! This is actually already being tracked by another issue on our repo - please refer to #3586 for more discussion.

/dup #3586

@ghost
Copy link

ghost commented Aug 19, 2021

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 Aug 19, 2021
@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 Aug 19, 2021
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
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
Milestone
No milestone
Development

No branches or pull requests
2 participants
@zadjii-msft @Convincible