-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
Duplicate shell entries in the drop down #3047
Comments
Hey @onovotny, we touched on this in the 0.5 release notes a bit. Your Windows PowerShell profile's guid doesn't match the "default" one (hold down Alt and click on Settings), so it's technically a different profile. If you'd like to override the default profile or reorder it, copy its guid over yours -- or just delete yours if you don't have any custom settings. |
You'll probably also see a duplicate pwsh.exe, eventually (if you install one in Program Files) -- the reason is the same. |
Might be worth a "reset to defaults" gesture in the UI? This wasn't really discoverable... |
That's a fair request. I think that on account of we're 0.5 and our settings model hasn't been declared stable, it's also not unfair to expect users to absorb some amount of "please delete your file to get back to the defaults." Moving forward, our "defaults" are way way better. It does glorious things if you delete |
Also, there's #947 for that request :) |
(Thanks for the suggestion! I know we'll need it going forward, and I think we have a backlog item for it. I can't find it at the moment.) |
Ding! |
Environment
Steps to reproduce
Add another profile in the json. Drop down shows too many.
Expected behavior
The list of profiles in the drop down should match the profiles.json
Actual behavior
An extra entry is in the list. There is no profile 5. What's strange is that when I launch that bogus profile, it doesn't look like the one I set up:
The "real" profile for Windows PowerShell looks like this:
Here's the profile list as shown by Terminal. Note the extra bogus profile that's not in the profiles.json
The text was updated successfully, but these errors were encountered: