Ricardo Signes

Sorry for my late reply! My first thought is: if you're using kill 0, you're doing it for the return value. I'd want kill to be fatal on in void...

What's in your shell's DOTDOTDOT_ORDER variable?

Yes. Also, who knew that there was a version subcommand? I sure forgot.

The gist, here for posterity: ``` perl #!/usr/bin/perl { package App::Cmd::Bug; use App::Cmd::Setup -app; BEGIN { $INC{"App/Cmd/Bug.pm"} = 1; } } { package App::Cmd::Bug::Command::foo; # Using Moose causes the usage...

Using Moose gets Moose::Object into `@INC` before App::Command::Command, which is put there by `use App::Cmd::Bug -command`, so the "wrong" new run. The only likely solution, here, is documentation.

Why did I never add the obvious comment: Yes, this would be cool.

- Jakob Voss [email protected] [2013-10-30T07:59:16] > Any arguments against letting > > myapp somecommand --help > > call > > myapp help somecommand Even I still do that. Go for...

Looks good to me. I think I'd prefer dropping the "did you mean the private writer?" in the case of a private writer. I can see arguments both ways, though,...

Putting aside the question of bogus metadata, it would be helpful if we could sort the version browser by version number rather than by upload. I realize this is non-standard,...

I pulled all the version of Perl listed in the `` in the HTML and wrote the code below. It's, uh, not my favorite code I've ever written, but it...