[SIDLAD]

This fixes it by putting PowerShell's call operator & in front of the command, so the quoted path runs as a command. I tested the fix by running the extension from source (F5 / Extension Development Host): PowerShell and cmd both activate the environment.

---

AI-assisted details (written with Claude Code)

Fixes #56.

Change (src/pixi/utils.ts)

• Adds execInfo.shellActivation with a single pwsh entry: { executable: '&', args: [pixi, 'shell', '--manifest-path', <manifest>, '-e', <env>] }.
  • The pwsh key covers both Windows PowerShell 5.1 and PowerShell 7.
  • quoteArgs leaves a lone & unquoted, so the result is & "C:\...\pixi.exe" shell ....
• Other shells aren't in the map, so they fall back to the existing activation unchanged (per getShellActivationCommand).
• Pulls the shared shell args into a shellArgs const to avoid duplication.

Checks

• npm run lint, npm run format:check and npm run compile all pass.

Testing

• Same machine and setup as the PR for Fails on Windows, when there is a space in the home directory path #8, run via F5 with both fixes applied:
  • PowerShell: & "C:\Users\First Last\.pixi\bin\pixi.EXE" shell --manifest-path D:\Projects\LearningMLDL\pixi.toml -e default → prompt becomes (LearningMLDL) PS …. Before this change, the same terminal failed with Unexpected token 'shell'.
  • Command Prompt: unchanged, "C:\…\pixi.EXE" shell … → (LearningMLDL) ….

Side note for anyone testing via F5: when the extension runs from a folder whose path doesn't contain renan-r-santos.pixi-code (e.g. a plain pixi-code clone), Python Environments' caller detection files the manager as ms-python.python:pixi. Selecting a Pixi env then fails with No environment manager found for [renan-r-santos.pixi-code:pixi]. For local testing only, I passed { extensionId: 'renan-r-santos.pixi-code' } to registerEnvironmentManager/registerPackageManager. That isn't part of this PR, but it could be worth doing for robustness.

Notes

• This is independent of the Fails on Windows, when there is a space in the home directory path #8 fix. Either can merge first.
• Add CLI options and use shell-hook for activation #26 (open) rewrites activation to use pixi shell-hook via shellActivation and would conflict with this. Its pwsh entry interpolates ${pixi} unquoted into (& ${shellHookCmd}), so it would hit the same spaced-path problem. If Add CLI options and use shell-hook for activation #26 lands instead, quoting pixi there would cover this case.

🤖 Generated with Claude Code