Matthew Kenigsberg

> could we add a case that says don't do autocomplete when you could have multiple targets? Yes

I wouldn't necessarily expect this edge case will be covered by the initial implementation, but it's probably a decent edge case to keep in mind at some point in the...

I believe the original design of layered activation said that development variables (e.g. PYTHONPATH) would only be set for the most recently activated environment. Currently we're not unsetting variables for...

> > and only create a development environment for a single, likely the last, activated environment > > yes I do recall us discussing and agreeing to this. One other...

No we pass `nix_bin` explicitly rather than using an environment variable: https://github.com/flox/flox/blob/e2d4ad168152ad4da091c61931cd6d86ca312bd7/crates/flox-rust-sdk/src/flox.rs#L80

> (And a workaround for the noob -- i.e. me -- would be welcome, here.) If you're in the runix repo, you can run `flox` or `nix` `develop .#runix`. Are...

> Alternatively, the crates.io pkg of runix could be updated if it's not too much trouble? The current one is 12 month old and this would allow users to include...

I think so long as we can represent all three states (flag passed with value, flag not passed and gets default value, flag passed with default value), I don't have...