Closed jonashaag closed 1 week ago
I'm not sure how pixi should deal with that as it is first parsed by the shell you are running in.
Normally you can escape this by using \
in front of chars you don't want your shell to run.
Since Pixi uses Deno's task shell I tried it in Deno:
❯ deno eval 'console.log(Deno.args)' xxx '*foo*'
[ "xxx", "*foo*" ]
Also in Bun:
❯ bun --print 'process.argv' xxx '*foo*'
[ "/opt/homebrew/Cellar/bun/1.1.12/bin/bun", "/private/tmp/[eval]", "*foo*" ]
IMO the arguments passed after the task name should not be evaluated in the Deno shell, but passed literally
bump!
Checks
[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest version of pixi, using
pixi --version
.Reproducible example
Issue description
Quoting is not passed to subcommand
Expected behavior
Quoting should be passed to subcommand