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

Re-Scan WSL distros at launch #1289

Closed
hbjydev opened this issue Jun 16, 2019 · 1 comment
Closed

Re-Scan WSL distros at launch #1289

hbjydev opened this issue Jun 16, 2019 · 1 comment
Labels
Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. 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

Comments

@hbjydev
Copy link

hbjydev commented Jun 16, 2019

Summary of the new feature/enhancement

I think it could be useful to have Cascadia re-scan the WSL distros every time it launches, so that installing a new WSL distro will reflect on the profiles menu.

Proposed technical implementation details (optional)

It would just run CascadiaSettings::_AppendWslProfiles every time the app loads up, so it gets them all and adds any new profiles necessary,
@hbjydev hbjydev added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 16, 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 16, 2019
@hbjydev hbjydev changed the title [Feature Request] Re-Scan WSL distros at launch Re-Scan WSL distros at launch Jun 16, 2019
@DHowett-MSFT
Copy link
Contributor

Hey, weird enough, this’ll be fixed by #754. There’s a spec review in progress for that feature at #1258.

@Forinil Forinil mentioned this issue Jun 28, 2019
Closed
42 tasks
@DHowett-MSFT DHowett-MSFT mentioned this issue Oct 17, 2019
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. 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
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@DHowett-MSFT @hbjydev