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.

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

Allow users to remove Powershell if Powershell Core or Powershell Preview is installed #10547

Closed
Tracked by #9997
williamhorning opened this issue Jul 2, 2021 · 8 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

@williamhorning
Copy link

Description of the new feature/enhancement

If the user has Powershell Core or Powershell Preview installed, allow them to remove the built in Windows Powershell profile. I would use this because I don't want to use the built in Windows Powershell, I would rather use Powershell Preview.

@williamhorning williamhorning added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jul 2, 2021
@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 Jul 2, 2021
@KalleOlaviNiemitalo
Copy link

Windows Terminal already lets you hide the profile.

image

@DHowett
Copy link
Member

DHowett commented Jul 2, 2021

We're working on a couple things to actually let you delete these. Sorry about that 😄

I'm gonna mark this one as a /dupe of #5482. When combined with #8324, it'll (1) generate the profile one time and (2) let you delete it without resurrecting it every time

@ghost
Copy link

ghost commented Jul 2, 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 Jul 2, 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 Jul 2, 2021
@williamhorning
Copy link
Author

Windows Terminal already lets you hide the profile.

image

@KalleOlaviNiemitalo Whenever I do that and save it, It reverts itself :|

We're working on a couple things to actually let you delete these. Sorry about that 😄

I'm gonna mark this one as a /dupe of #5482. When combined with #8324, it'll (1) generate the profile one time and (2) let you delete it without resurrecting it every time

Thanks for letting me know!

@KalleOlaviNiemitalo
Copy link

Whenever I do that and save it, It reverts itself :|

Huh, that's not what happens here with Windows Terminal 1.8.1521.0. Which version are you using?

@williamhorning
Copy link
Author

Whenever I do that and save it, It reverts itself :|

Huh, that's not what happens here with Windows Terminal 1.8.1521.0. Which version are you using?

I use Terminal Preview 1.9.1523.0, but I found a workaround in #6016 (comment)

@DaveEM
Copy link

DaveEM commented Jul 20, 2021

@DHowett - Do #5482 and #8324 really resolve this issue? While those will keep the profile from being restored if it is deleted from the config file, the Settings UI as of Windows Terminal version 1.9.1942.0 won't let you delete the Windows PowerShell profile. The "Delete Profile" button is greyed out and it says, "This profile cannot be deleted because it is included by default."

@williamhorning
Copy link
Author

williamhorning commented Jul 21, 2021 via email

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

No branches or pull requests

4 participants