docs: clarify in CLI that run can also take commands

[twrightsman]

I didn't realize pixi run could also execute arbitrary commands in an environment and thought only pre-defined tasks, based on the CLI help text. This small patch makes this a little clearer for folks not reading the online manual.

[tdejager]

Thanks! Do you think command covers the terminology you expected or something like system command/executable in environment make sense?

[twrightsman]

Good question @tdejager . I think something more along the lines of "The predefined pixi task or ad-hoc shell command you want to run in the project's environment" would be most explicit for me. How does that sound?

[ruben-arts]

The only thing to keep in mind is that you run it in the denk task shell, so only commands in that set can be run. E.g. not test like in bash.

So perhaps "ad-hoc task command" would fit better with the implementation.

[twrightsman]

Ah, I see. Then perhaps:

The pixi task or a deno task shell command you want to run in the project's environment, which can be an executable in the environment's PATH.

This follows more closely to what the online docs say. I wouldn't necessarily expect a user to know what a "deno task shell" is in order to understand they can execute binaries in the environment with pixi run 🙂

[tdejager]

Sounds good, let's give it a try!