-
Notifications
You must be signed in to change notification settings - Fork 8.4k
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
Profile is being auto updated with PowerShellCore #4532
Comments
If they are installed and on your PATH then simply relaunching Terminal should pop them up as it detects new console apps and terminals during loading of Terminal itself. |
@WSLUser you can't do that when I have no way of adding pwsh to have it call PowerShell 7. |
Do both Powershell options appear for you from the drop down menu? I would rename one of the executables such as pwsh6.exe. I only have 7 installed and it works just fine. The problem is while Terminal can dynamically find different Powershells on the system, it is not able to determine which pwsh to execute, so it defaults to whatever appears on your PATH first. |
Also adding
when both 6 and 7 are there in your profile is redundant. |
So, this is a bit of an artifact of how dynamic profiles work. #3231 (comment) has a bit more information. In short, Terminal detects some known powershell locations (version < 0.9: only one powershell will be detected; version >= 0.9: all known powershell instances will be detected) and automatically generates profiles for them. The dynamic profile system is, perhaps, a bit unintuitive. When a profile has a What's happening here is that you're changing the To suppress the dynamic one, set *: it is a misunderstanding that birds do not accept their own young if a human has set a |
I'm not sure I follow @DHowett . I set my profile to this and it still won't work, it actually errors because it can't find the default profile:
|
In even shorter: do not change Setting |
Ah! Gotcha. |
Environment
Steps to reproduce
list[]
:list[]
.Expected behavior
The ability to add PowerShell 6 and PowerShell 7 to my Terminal.
Actual behavior
The block I remove for
Windows.Terminal.PowerShellCore
continues to be added back, and the entries I have for PowerShell 6 and 7 seem to be ignored.I am trying to add the following to my profile in order to get PowerShell 6 and 7 in my terminal session:
However ever time I save the changes the contents are being changed to this (notice the last item:
I may be doing something wrong, but I have not been able to determine what it is.
For those that want to see this in action:
The text was updated successfully, but these errors were encountered: