Default command not always run when a global option is used

[DavidJRobertson]

Default command not always run when a global option is used

[ggilder]

I'm afraid I'm not able to reproduce the behavior you reported. I tried the script you posted, with a mock substituted for the Woody class, and running the executable with no command always ran the compile command, whether I specified --dir or not.

I put up a simplified test script here: https://gist.github.com/4298299

That can be run on its own. Could you try running that and let me know if you see different results? And if so, please let me know system and ruby version.

[DavidJRobertson]

The problem only seems to occur if the directory used with the --dir option begins with the letter d.
When I tested the application the first time I ran woody --dir demosite, and the deploy method was called, rather than compile.

With the tester.rb script you have provided:

➜  demos  ./tester.rb
initialized with .
Compile called
➜  demos  ./tester.rb --dir dwhatever
initialized with dwhatever
Deploy called

[ggilder]

Ah, so I'm guessing it has to do with the command alias then (which in your example is "d" for deploy). I'll do some more testing and see if I can narrow down the bug.

[DavidJRobertson]

I've just tried commenting out the alias lines, and now the script behaves as it should - must be something to do with the command aliases then.

[ggilder]

As it turns out, this issue was already fixed in #39 — I just hadn't released a new version incorporating it yet. I've just released 4.1.3 which should fix the issue. Please update to 4.1.3 and let me know if you still see any problems. Command aliases should also work normally.

[DavidJRobertson]

Works perfectly now, thanks.