So, this is a "clever" one where if you do echo $(boot2docker ip) it only provides the IP address, but it's caused enough confusion that I'm definitely +1 on making it just return the IP without any extra text so we stop having to explain how "clever" it is and have it instead just do what people expect it to. 😄

Hehe, yes, I didn’t know that! :) Just fixed my scripts.

Though after eating stdout, the remaining output is sent to stderr (The VM’s Host only IP address… and the blank lines), which is not very “unixy" - usually stderr is reserved for errors only, which you don’t want to ignore/silence, so it’s a bit disturbing to live with the extra (and incomplete since the IP is “eaten” by stdout) output all the time.

Also it’s a bit extraneous and arguably not a very good fit with the terseness / “silence is golden” Unix philosophy “rule": http://homepage.cs.uri.edu/~thenry/resources/unix_art/ch11s09.html
from http://homepage.cs.uri.edu/~thenry/resources/unix_art/ch01s06.html

I guess it comes down to how well you want to fit into a unix scripting world vs an interactive shell world.

On Nov 12, 2014, at 5:00 , Tianon Gravi notifications@github.com wrote:

So, this is a "clever" one where if you do echo $(boot2docker ip) it only provides the IP address, but it's caused enough confusion that I'm definitely +1 on making it just return the IP without any extra text so we stop having to explain how "clever" it is and have it instead just do what people expect it to.

—
Reply to this email directly or view it on GitHub #310 (comment).

+1

Another workaround is to redirect stderr;

ping $(boot2docker ip 2>/dev/null)