# Default environment activation in docs tutorial should look different IMO

**URL:** <https://discourse.flox.dev/t/default-environment-activation-in-docs-tutorial-should-look-different-imo/1114>\
**Category:** Feature Requests\
**Created:** [April 4, 2025, 6:56pm UTC](https://discourse.flox.dev/t/default-environment-activation-in-docs-tutorial-should-look-different-imo/1114 "2025-04-04T18:56:31Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![maxgitnet](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/maxgitnet/32/758_2.png) [@maxgitnet](https://discourse.flox.dev/u/maxgitnet)\
**Post date:** [April 4, 2025, 6:56pm UTC](https://discourse.flox.dev/t/default-environment-activation-in-docs-tutorial-should-look-different-imo/1114/1 "2025-04-04T18:56:31Z")

</div>

Hello,  
This is the suggested line to add to .zshrc / .bashrc to start the default environment.

```auto
eval "$(flox activate -m run)"

```

(Reference)

> **[The default environment - Flox Docs](https://flox.dev/docs/tutorials/default-environment/#:~:text=Add%20the%20following%20line)**
>
> Using Flox as your system package manager

I think you should change it in the docs to:

```auto
eval "$(flox activate -d "$HOME" -m run)"

```

because the original line assumes that the user opens the terminal in $HOME.

This may not always be the case. Then I either get an error because no .flox folder is there, or it would start the local Flox environment instead of the default one, requiring me to manually start the default environment.

Or is there a good reason why it shouldn’t be like I suggest?

---

<div class="post-metadata">

**Author:** ![ysndr](https://yyz2.discourse-cdn.com/flex036/user_avatar/discourse.flox.dev/ysndr/32/340_2.png) [@ysndr](https://discourse.flox.dev/u/ysndr)\
**Post date:** [April 9, 2025, 9:40am UTC](https://discourse.flox.dev/t/default-environment-activation-in-docs-tutorial-should-look-different-imo/1114/2 "2025-04-09T09:40:01Z")

</div>

Hej, and welcome!

I think you’re right we could be more specific there.  
Generally I believe we’ll default to the “default” env in many cases to avoid this issue, but activating other environments than the default one is probably unexpected.

Thanks for bringing this to our attention.