Make --directory a global argument

[charliermarsh]

Summary

Cargo makes this global (and uses the same technique). It's still hidden so we can always decide to remove it.

[bluss]

Changing directory is a different thing and makes uv run harder to use like that (if you pass relative paths to an uv run command, it might not work so well.)

[charliermarsh]

What's harder about it? Why is it wrong to resolve paths relative to the provided directory?

[charliermarsh]

(I mean, it's easy to change -- we just track a current directory globally in uv-fs, add a setter, and always read from there rather than using CWD.)

[bluss]

I'm thinking that you have something like

$ uv --directory path/to/proj run the_command --flag ./myfile.txt
# <------- uv run part ---------> <-- regular command part  ---->

Ideally the uv run part should just be transparent. It brings forth the environment in where the program executes. The regular command line part of the command shouldn't have to change.

One reason why it's wrong to resolve myfile.txt relative to the given directory is that the user probably autocompleted it from their current directory. It's hard to use interactively (and hard to use in scripts as well, except there you'd probably just have to remember to abspath everything.)

[charliermarsh]

That makes sense. I can change it up.