Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--enter behaving odd in a be activate environment #30

Closed
mottosso opened this issue Jul 2, 2015 · 0 comments
Closed

--enter behaving odd in a be activate environment #30

mottosso opened this issue Jul 2, 2015 · 0 comments
Labels

Comments

@mottosso
Copy link
Owner

mottosso commented Jul 2, 2015

Turns out that be activate in Bash writes to BE_CWD which is considered the current working directory. In combination with --enter, this causes the old BE_CWD to overwrite the actual current working directory, thus causing be to enter into the wrong project.

@mottosso mottosso added the bug label Jul 2, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant