# Environment activation

**URL:** <https://discourse.flox.dev/t/environment-activation/455>\
**Category:** Bug Reports\
**Tags:** closed\
**Created:** [October 30, 2022, 9:07pm UTC](https://discourse.flox.dev/t/environment-activation/455 "2022-10-30T21:07:22Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![etorreborre](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/etorreborre/32/428_2.png) [@etorreborre](https://discourse.flox.dev/u/etorreborre)\
**Post date:** [October 30, 2022, 9:07pm UTC](https://discourse.flox.dev/t/environment-activation/455/1 "2022-10-30T21:07:22Z")

</div>

Something does not seem to work for me:

```auto
~/projects/rust/edits on main
± flox environments
etorreborre/default
    Alias default
    System x86_64-darwin
    Path /Users/etorreborre/.local/share/flox/environments/etorreborre/default
    Curr Gen 30 (remote 4)
    Commit 40c5130 (remote 277089a)

etorreborre/rust
    Alias rust
    System x86_64-darwin
    Path /Users/etorreborre/.local/share/flox/environments/etorreborre/rust
    Curr Gen 1

[flox]
~/projects/rust/edits on main
± flox activate -e rust
[flox]
~/projects/rust/edits on main
± flox list
etorreborre/default
    Alias default
    System x86_64-darwin
    Path /Users/etorreborre/.local/share/flox/environments/etorreborre/default
    Curr Gen 30

Packages
    0 unstable.nixpkgs-flox.cargo-tarpaulin.0_22_0
    1 unstable.nixpkgs-flox.cargo-tarpaulin.0_22_0

```

I was expecting `flox list` to show the rust environment at Gen. 1. This is with 0.0.6-rc45.

---

<div class="post-metadata">

**Author:** ![limeytexan](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/limeytexan/32/10_2.png) [@limeytexan](https://discourse.flox.dev/u/limeytexan)\
**Post date:** [October 30, 2022, 9:20pm UTC](https://discourse.flox.dev/t/environment-activation/455/2 "2022-10-30T21:20:18Z")

</div>

We’ve received this feedback from others as well. The flox “environment” subcommands don’t [yet] respect the context of the “active” environment, so will always report the “default” environment if another hasn’t been specified.

Bottom line - `flox list -e rust` shows you the contents of the “rust” environment, and `flox list` shows you the contents of the “default” environment regardless which other environments have been activated. We’re working to change that to be context-sensitive, perhaps even prompting the user to select which of the currently-activated environments they want to list.

Thanks again for all the great feedback!

---

<div class="post-metadata">

**Author:** ![robinbrantley](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/robinbrantley/32/39_2.png) [@robinbrantley](https://discourse.flox.dev/u/robinbrantley)\
**Post date:** [November 3, 2022, 11:38am UTC](https://discourse.flox.dev/t/environment-activation/455/3 "2022-11-03T11:38:20Z")

</div>

> [@limeytexan](#):
>
> We’ve received this feedback from others as well. The flox “environment” subcommands don’t [yet] respect the context of the “active” environment, so will always report the “default” environment if another hasn’t been specified.

Just wanted to confirm this is on our list of things to do and is being prioritised. It’s going to take some time but we will be sure to let you know once it has been done. 🙂