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

If setting change requires restart, notify user #1253

Open
bitcrazed opened this issue Jun 13, 2019 · 2 comments
Open

If setting change requires restart, notify user #1253

bitcrazed opened this issue Jun 13, 2019 · 2 comments
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal.
Milestone
Backlog

Comments

@bitcrazed
Copy link
Contributor

Summary

If a setting is changed that requires the Terminal to restart in order for the setting change to take effect, consider displaying a message to the user prompting them to restart their Terminal.

Also, consider making it easier to identify settings that require a Terminal restart if changed, perhaps using an emoji/visual glyph of some kind?

Related

This feature is related to #1252 suggesting that the Terminal should support restart/resume.

Proposed technical implementation details (optional)
@bitcrazed bitcrazed added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 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 Jun 13, 2019
@DHowett-MSFT
Copy link
Contributor

This just needs some good good settings UI.

@DHowett-MSFT DHowett-MSFT added Area-Settings Issues related to settings and customizability, for console or terminal Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal. and removed 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 labels Jun 18, 2019
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jun 18, 2019
@DHowett-MSFT
Copy link
Contributor

DHowett-MSFT commented Jun 18, 2019 •
edited

This just needs to be parented to some good good settings UI deliverable.

@zadjii-msft zadjii-msft added this to the Terminal Backlog milestone Jun 19, 2019
@bitcrazed bitcrazed mentioned this issue Oct 7, 2019
Closed
@zadjii-msft zadjii-msft modified the milestones: Terminal Backlog, Backlog Jan 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Area-Settings Issues related to settings and customizability, for console or terminal Issue-Task It's a feature request, but it doesn't really need a major design. Product-Terminal The new Windows Terminal.
Projects
None yet
Milestone
Backlog
Development

No branches or pull requests
4 participants
@bitcrazed @carlos-zamora @DHowett-MSFT @zadjii-msft