flox activate reactivates the environment

[ghudgins]

When I launch a vscode shell from an active Flox environment
I need a flox activate to allow me to refresh the environment
So I can avoid having to close and re-open vscode to get environment hook updates, etc

Acceptance Criteria

Given I have flox activate a path environment in the current directory
When I run flox activate again from the same directory
Then I see the environment is activated again (equivalent of exit && flox activate)

[ghudgins]

+1 from user research

[mkenigs]

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 && flox activate does solve the vscode case?

[ghudgins]

try this:

• in a project directory create an environment
• activate it
• enter the IDE
• attempt to get dependencies in path...fail
• attempt to activate...fail

vs. if I open IDE before I activate I can get it to work

Does exit && flox activate solve the vscode case?

no because the IDE's terminal was always spawned inside of an env

[mkenigs]

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

[ghudgins]

fair enough! happy to morph this issue into another solution if there's a better way