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

Feature Request: Allow users to re-scan for profiles #1518

Closed
beforan opened this issue Jun 24, 2019 · 3 comments
Closed

Feature Request: Allow users to re-scan for profiles #1518

beforan opened this issue Jun 24, 2019 · 3 comments
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 Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing.

Comments

@beforan
Copy link

beforan commented Jun 24, 2019 •
edited
Loading

Summary of the new feature/enhancement

Currently when you install/first run (?) the Windows Terminal, it adds profiles for the various shells you have installed (e.g. Command Prompt, Powershell 5, WSL Debian).

If you later install further shells on your system (e.g. Powershell Core (6 or later), Ubuntu or other WSL distros) you have to manually configure profiles for these, even though Terminal is capable of detecting them.

Could there be an item in the profiles/settings dropdown menu to scan for profiles on demand? It would just run the same scan as is currently performed at install/first run.

That way after installing additional shells, it would be one click (or maybe 2 if there was a confirmation dialog of which found profiles to add) to get profiles for them.
@beforan beforan added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 24, 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 24, 2019
@ghost
Copy link

ghost commented Jun 24, 2019

For now, you can delete the profiles.json file and it will refresh the next time you launch the terminal

@DHowett-MSFT
Copy link
Contributor

DHowett-MSFT commented Jun 24, 2019 •
edited
Loading

#1321 #754 #1258 thanks for playing!

@DHowett-MSFT DHowett-MSFT added the Resolution-Duplicate There's another issue on the tracker that's pretty much the same thing. label Jun 24, 2019
@DHowett-MSFT
Copy link
Contributor

(Sorry to be terse: we have hundreds of new issues, and I'm trying to reduce repository noise. This one is less discoverable than most.)

@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 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
@beforan @DHowett-MSFT