Matthew Kenigsberg

I think we could do this for `activate -d` but it probably wouldn't make sense for `activate -r`

Thanks for writing that down @limeytexan! I think for clarity we should split this into two parts: 1. Add an option to decide which outputs to install. It's pretty clear...

We'll come back to this once the manifest format is stable

I don't quite understand the vscode motivation combined with the AC. Does `exit && flox activate` solve the vscode case? If not, how would making `flox activate` do what `exit...

> * managed environments no longer hide the manifest.toml and manifest.lock file Is there any reason we shouldn't still hide the lock? > ``` > ❌ ERROR: Your environment has...

> I agree, the managed parts are generations, but the message @mkenigs referred to was differentiating between **types** of environments: `path` vs. `managed`. The message is used if you try...

Hmm it looks like vscode is inheriting environment variables (e.g. `_FLOX_ACTIVE_ENVIRONMENTS`) but somehow `PATH` is getting messed up. Needs some more investigation

> @mkenigs does that address your concern? Yep, thanks!

@ghudgins @jennymahmoudi ready for review

We're not paging for search so that could be an issue. Or maybe we're not correctly setting page size