Daniel Martí

Where is this documented?

Hi, thanks for sending a pull request! I'm sure you have seen, but much like Go's `os/exec`, we support command arguments as a list of strings, which sidesteps this issue...

Closing for now, as I explained in https://github.com/cue-lang/cue/issues/3238#issuecomment-2217486068. Thanks for contributing!

@ColemanTom refers to the `--binary-next-line` option, which affects `&&` and `||` as binary command operators. `shfmt` puts these at the end of a line by default instead of at the...

As of f93b6b9a559f755a330938401cbe3483b9218662, evalv3 (the default) seems to hang with the original testscript, consuming my memory rather quickly. So I don't think this is an evalv3 win anymore :)

Still happens as of 9ca9609cf83cf5fa423e4ef5458e12774693a29c.

Thanks. How often does this realistically come up? If we add this, I would rather not add new flags. We can tweak `--find` and `--list` so that they also accept...

> Every time one wants to use `--find`/`--list` with `xargs` or any other tool like `sort`. You only need to null-separate arguments when they could contain newlines though. I have...

Ah of course. For some reason I misremembered `xargs` to only split on newlines, but it does split on spaces too.

See the snippet I shared earlier: https://github.com/mvdan/xurls/blob/c5b6e994e5db07c3f691bbb8c044b34dd20720f8/cmd/xurls/main.go#L36-L44 In particular the presence of `IsBoolFlag`.