GeezerVison

• Resolves issue Implement shell globbing #954.
• Code is rebased on origin/master.
• Add tests that fail without your changes. Pending
• Update all relevant documentation. Pending

Enable path globbing for native commands

E.g. ls *.md expands to ls /path/to/README.md /path/to/CHANGELOG.md

If expansion fails, the argument is sent literally, so ls foo* results in /usr/bin/ls: cannot access foo*: No such file or directory.

Don't glob expand if the verbatim marker was used.

/cc Jason Shirk (@lzybkr) James Truher (@JamesWTruher)

After tracing what the native command parameter binder does, it seems most reasonable to add this logic to appendOneNativeArgument. I know that doesn't sound right, but in fact it already deals with being sent an argument that gets expanded to a list. However I could be completely wrong, as the code around here is a bit strange.

When a parameter.ParameterNameSpecified is true, we don't want to glob, as this correlates to -flag. Moreover, the CommandParameterInternal should probably be updated to interpret --flag as a Parameter (instead of an Argument); as it does not currently.

We want to glob when parameter.ArgumentSpecified is true, and only once it's been converted to a string (or expanded to a set of strings) (which happens in the poorly named appendOneNativeArgument function).

We do not want to glob if the --% verbatim marker was seen.

I need to add tests, but figured I'd get this up for review.

Also I already have one known bug: globbing doesn't appear to work for .dotfiles. So although *.md works, .gi* and *git* does not work. But it doesn't have anything to do with these changes, it fails similarly for Get-ChildItem too. I'll file a bug report tomorrow.