-
```
brew install autoenv
source /usr/local/opt/autoenv/activate.sh
-bash: /usr/local/opt/autoenv/activate.sh: line 115: syntax error near unexpected token `('
-bash: /usr/local/opt/autoenv/activate.s…
-
Hi, I sort of have 2 things I've discovered about autoenv. First one is pretty straightforward, it does not seem to check if .env is a dir or file:
```
autoenv % pwd -P
/private/tmp/autoenv
autoenv …
-
When entering an autoenv for the first time, after authorizing the .env file, bash raises:
bash: /home/user/.autoenv_authorized: cannot overwrite existing file
This is triggered by set -o noclobber, …
-
`/usr/local/opt/autoenv/activate.sh` does not exist when installed via brew (for me at least). Also, if a user has installed brew into a different location, the path to autoenv may be different and `b…
-
Bad form on my part to have spaces, but I think this should probably be fixed. Autoenv doesn't seem to work when the path to the working directory has spaces.
If the pwd is "/Users/me/my project/", I…
-
-
I'm not sure if this is a problem with my setup or if it's just a limitation, but it would be nice if I could get autoenv source the `.env` when I use `workon` from virtualenvwrapper to change to a pr…
-
I have a trouble with [last-working-dir](https://github.com/robbyrussell/oh-my-zsh/blob/master/plugins/last-working-dir/last-working-dir.plugin.zsh) zsh plugin. This plugin absolutely doesn't work wit…
-
The docs claim that Foreman .env should work however the standard format of a .env file is KEY=VALUE pairs. It looks like autoenv just sources the .env file so these pairs are not being exported.
Am …
-
Homebrew uses the `0.1.0` release of `autoenv` that was released on February 15th, 2012. I just ran into a bug with whitespace handling that is broken in `0.1.0` but has been fixed since then. Can you…