Add additional PowerShell Core paths (preview, scoop, etc.) to dynamic profile generator #2300
Comments
|
We should handle this as part of a powershell core dynamic profile generator! |
|
Therefore, I am converting this issue to be the master task for "Switch PSCore to a dynamic profile generator". |
|
@zadjii-msft - thoughts:
|
|
Eh, yea this should probably be re-purposed for those things. Frankly I don't know enough about PSCore to implement preview, scoop, etc. support myself, but I'm sure that an enterprising community member could always update the |
|
I'm taking a crack at this!
|
|
The "latest good" (determined by a sorting algorithm ;P) one gets the legacy "Powershell Core" GUID :) // Total sort order:
// 6-preview (wow) < 6-preview (native) < 7-preview (native) < 6 (wow) < 6 (native) < 7 (native)
uint8_t Radix() const
{
return (preview ? 0b00000000 : 0b10000000) | ((majorVersion - 6) << 4) | (nativeArchitecture ? 0b1000 : 0x0000);
} |
|
@SteveL-MSFT quick questions I wanted to run by you, all related to powershell branding. When we're generating automatic profiles for Powershell instances:
Right now, my total global sort order is this: I'm not sure where to slot "program files", "dotnet global" and "windows store" to the sort order. 😄 |
|
@DHowett-MSFT Casing is "PowerShell" always. I wouldn't show version numbers. You're saying "Core" is dropped after 7 is released? I'd prefer the pwsh.exe that is first in the path. |
|
From a branding perspective, I would suggest differentiating:
(6.0 is out of support already) I don't think 6.x-Preview is needed since we have stable releases of those and no more previews for 6.x ever. |
…4273) This pull request teaches the PowerShell Core generator about a bunch of different locations in which it might find a PowerShell. These instances will be sorted, a leader will be elected, and that leader will be promoted and given the vaunted title of "PowerShell". Names will be generated for the rest. The sort order is documented in the comments, but that comment will be replicated here: ``` // <-- Less Valued .................................... More Valued --> // | All instances of PS 6 | All PS7 | // | Preview | Stable | ~~~ | // | Non-Native | Native | Non-Native | Native | ~~~ | // | Trd | Pack | Trd | Pack | Trd | Pack | Trd | Pack | ~~~ | // (where Pack is a stand-in for store, scoop, dotnet, though they have their own orders, // and Trd is a stand-in for "Traditional" (Program Files)) ``` Closes #2300
|
After doing this it doesn't appear in the list of profiles... Am I missing something? |
|
Unless you’re running the latest internal-to-microsoft build that was released last night around midnight, you’re missing a version of Windows Terminal that actually has this feature in it 😅 |
|
(If you aren’t: check the store for updates, then hit me back!) |
|
Windows Terminal version 0.8.10261.0 My dilemma has been that I want to use Windows Terminal with both PowerShell GA and Preview versions. But it seems that I can't, as it only pick one of the installed version.
If I remove the GA version, then it grabs the Preview:
|
|
Well yes, again, this is because you’re using a released version of Terminal that predates this feature being added and this bug being closed. That is how we handle all bugs in this repository: they are closed when the code change is made, and an announcement is posted when a release is available that contains the change. |
|
Thank You All for your hard work! I love Windows Terminal. |
|
🎉This issue was addressed in #4273, which has now been successfully released as Handy links: |
depends on #754
Description of the new feature/enhancement
To include PowerShell 7 Preview.2 in the list of consoles if is already installed in the system.
I got both PowerShell Core GA and Preview installed for some time. And, the last few updates of Windows Terminal, is not automatically showing in the console list.
The text was updated successfully, but these errors were encountered: