docs: Add PowerShell example

[jahanson]

I added an example for PowerShell and profile location. Please let me know if you have any questions.

[jahanson]

I'm not familiar enough with autofix.ci to understand why it reverted my changes.

[fgilcc]

I'm guessing you probably need to update documentation in the rust function and it will update everywhere else.

src/cli/activate.rs

[jdx]

is the ampersand a typo?

[jahanson]

No, this invokes the command in a non-blocking way. Background Operator

[jdx]

why would we want that here? Isn't that going to cause the output to not even be parsed by powershell? even if it was, wouldn't it mean the next command might not have the tools setup?

[jdx]

I'm also confused why it's at the beginning here but more so why we would want to background this

[jahanson]

$(mise activate pwsh) | Out-String | Invoke-Expression works just the same. But it seems Invoke-Expression -Command $(mise activate pwsh | Out-String) causes an issue with the parameter length. So the piping is preferred.
We can change it to $(mise activate pwsh) | Out-String | Invoke-Expression if it is preferred.

[jdx]

that's what @fgilcc put in the readme and we should at least be consistent. I think we should stick with what @fgilcc has unless they think we should do something different.

If we do want to change it then it would need to happen everywhere in the docs.

[jahanson]

You know, I didn't even see it in the README to be honest. Sorry about that. I'm up for either approach. I'm just personally a fan of modifying my own profile script instead of a script adding it to the end. In the end, I was just following the style of the other nearby examples. I hadn't even thought to look outside the docs.

[jdx]

modifying my own profile script instead of a script adding it to the end. In the end

same here, although with mise it actually is important that it gets loaded last or else the tools might not be in the front of PATH so it's good guidance for us to just tell users to put it at the end