…rectory tree I wanted to define my dotfile as: `config.vagrant.dotfile_name = "~/.vagrant-projectname"` and noticed that the full path wasn't expanded as expected. This patch allows the vagrant file to be placed anywhere on the filesystem.
Puppet module-path were re-ordered by Vagrant due to the use of a hash. This could lead to unpredictable results.
There was an issue before where the stdin buffer would always have space so it would always yield that block and Ruby would spin at 100%. Now we require all callers to say what they want to listen for. This drops CPU down to almost nothing. See GH-832
Easy commands can now easily get arguments from the command line. Using `arg`, you can get named arguments on the command line, such as "--foo" or "-f" With `arg_extra`, you can get any remaining arguments after a "--" on the command line, which is a common pattern used to grab longer parameters.
Some new APIs were added to the easy command operations. `info`, `error`, and `success` are simple ways to output messages to the UI without resorting to "puts" in Ruby, since the Vagrant UI object is the idiomatic way to do communication with the world. Additionally, `argv` was added which gives commands access to the command-line arguments that are remaining that does not include the vagrant binary or subcommand. Also, behavior was changed: Previously, easy commands would run for every target VM. Now, it is only run once with the primary VM. In the next commit, I plan on adding a new flag that signifies an easy command is meant to work with a named VM.
…, a socket connect to localhost 2222 results in ENETUNREACH which needs to be caught as per this patch.