Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Add "eval" to every invocation of "docker-machine env" #795

Merged
merged 1 commit into from
Mar 17, 2015

Conversation

tianon
Copy link
Contributor

@tianon tianon commented Mar 17, 2015

See http://unix.stackexchange.com/a/181581 for the rationale behind this change (ie, better compatibility in the future, especially if env ever has to get more complex logic performed within the user's shell, since a workaround for one of the issues this solves is already in place).

See also moby/moby#11429, boot2docker/boot2docker#716, and boot2docker/boot2docker#786.

See http://unix.stackexchange.com/a/181581 for the rationale behind this change.

Signed-off-by: Andrew "Tianon" Page <admwiggin@gmail.com>
@ehazlett
Copy link
Contributor

LGTM

@ehazlett
Copy link
Contributor

Thanks!

ehazlett added a commit that referenced this pull request Mar 17, 2015
Add "eval" to every invocation of "docker-machine env"
@ehazlett ehazlett merged commit 89ea1ed into docker:master Mar 17, 2015
@tianon tianon deleted the eval-env branch March 17, 2015 02:57
@tianon
Copy link
Contributor Author

tianon commented Mar 17, 2015

❤️

@huslage
Copy link
Contributor

huslage commented Apr 9, 2015

This breaks the user experience. No one wants to run eval against anything. It's basically treating an edge case as if it were a major issue.

@md5
Copy link

md5 commented Apr 9, 2015

This breaks the user experience. No one wants to run eval against anything. It's basically treating an edge case as if it were a major issue.

It's an edge case that is very confusing for newcomers. I think this is a good change.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants