Invalid $OLDPWD: command "cd -" not working anymore

[poncki]

Hello.

While fixing #125 an error was introduced in ae84a55.
After cd <dir> the $OLDPWD variable is set to a wrong value (a new directory, not the old one) and cd - is not working anymore. Probably this is an effect of setting $PWD in line 14...

pnc

[dasJ]

Does #145 fix this for you?

[carhartl]

I'm having the same issue, but I'm not sure whether that may be my zsh setup or not...

[carhartl]

So basically what I did to fix this for me was moving this line: https://github.com/kennethreitz/autoenv/blob/7eb70eca0039f757525a2f88f008e647a492d7f1/activate.sh#L14

into the subshell:

  # Discover all files we need to source
  # We do this in a subshell so we can cd/chdir
  _files="`
    command -v chdir >/dev/null 2>&1 && \chdir "${_pwd}" || builtin cd "${_pwd}"
    _hadone=''
    while :; do
      _file="$(pwd -P)/${AUTOENV_ENV_FILENAME}"
      if [ -f "${_file}" ]; then
        if [ -z "${_hadone}" ]; then
          echo -n "${_file}"
          _hadone='1'
        else
          echo -n "
${_file}"
        fi
      fi
      [ "$(pwd -P)" = "${_mountpoint}" ] && break
      command -v chdir >/dev/null 2>&1 && \chdir "$(pwd -P)/.." || builtin cd "$(pwd -P)/.."
    done

Afterwards the value of $OLDPWD was intact and cd - worked again. Everything seems to work, though I didn't run any tests yet, just tried it out with an existing .env file.

[n8henrie]

Also suddenly noticed cd - not working, eventually discovered $OLDPWD and can confirm it was incorrect.

Took a fair amount of Googling to find this, the patch fixes the issue for me as well.

EDIT: Clarify, "the patch" is #149

[dasJ]

As #149 is merged, is this fixed for you?

[carhartl]

When homebrew user, while waiting for a new release to be pushed, something like this formalu may help: https://gist.github.com/carhartl/495c498aa1a1ef8a561d2ad53c52b3d6

You'd need to execute brew install --devel autoenv

[carhartl]

Though yeah, might be easier to source activate.sh from somewhere else!

[carhartl]

And the easiest seems to be:

$ brew uninstall autoenv
$ brew cleanup
$ brew install --HEAD autoenv

[n8henrie]

Yes, issue now seems resolved by installing from HEAD. Thank you!

EDIT: (I am unable to close as I didn't open, @poncki may be able to though.)

[henrahmagix]

I just came across this problem myself, and installing from HEAD has worked.

Can there please be a stable release soon to homebrew?

[pv8]

The release v0.2.1 doesn't actually include the fix for issue #141.

This release is on commit 92d2f3b (Oct 18, 2016) and the fix is on 6c55ec3 (Nov 11, 2016).

[dyson]

This just got me as well. Would be really great to get a new release out.