Activity (RSS)

This is a globally useful command, and is required in the runner to make some of these other changes so it should be abstracted from Commander::Command

Dope, I like it.

Remove the requirement to specify the program name.

program :name, 'Foo Bar'

With a change to Commander::Runner

    def program_defaults
      return :help_...

I think there is a ticket for --config already, but I like the additional info here. One thing I want to be careful with is cluttering EVERY executable with to ...

It'd be handy if commander also looked after config files.

eg.

$ commander --configure-list
Reading config file ~/.commander/commanderrc ...

  verbose = ...

Hmm I didnt think of that. I will take a look and see if it wont be much trouble to allow alteration of global messages while retaining their default functional...

Release: 3.1.8

The global default option appearing in the help message can't be overriden.

global_option '--help', "Tell you stuff you don't know"

GLOBAL ...

Ah yes, I am aware of this and forgot to create a ticket thank you! I will abstract the same functionality that Commander::Command uses for this

Release: 3.1.8

When the global_option is used only the first format of the option is shown in the help. (ie. it doesn't show both the short and the long formats...

Haha sorry just having some fun :), 'brainstorming' or 'ideas' would be a more appropriate tag haha..

As for the use-case for regexp matching I am having a hard...

Useful - yes. IMHO, anything that shifts work from the user to the command is a good thing.

(BTW what's with the "crazies"?)

What we have is not good enough, need to use BlankSlate or equiv when methods are added to Object etc

I think some are using #say, which print to STDOUT

Currently the following outputs due to the new exception rescuing:

Process interrupted
error: 
Process interrupted. Use --trace to view backtrace

Useful ? yes no maybe so?

Consider changing when_called so that |args, options| becomes |options, a, b, c| etc so that Ruby 1.9 users can take advantage of expanding args with 1.9.x para...

Start migration from version -> version docs

Require that devs explicitly require 'commander/import' which in turn imports highline as well .. otherwise require 'commander' for access to commands for testi...

Load options from a file much like spec.opts stores theirs.

Clean up Highline paging (its ugly) and use it to act much like less

Finish / add more documentation on the github page(s) for commander.

Perhaps sub-command options should inherit the globals, in cases such as --verbose this would prevent the need to do things like:

global_option('--verbose'){...

Will help clean things up a bit since the formatters must use $terminal.color

Alternative to the default ASCII terminal formatter, have a compact one similar to gem help

Allow these just like the main command itself can have arbitrary help blocks

Although in most cases this is most likely not an issue, it would be nice to have the ability to override these at a sub-command level.

Ensure everything is good to go for 1.9.x :)

It is sometimes hard to debug options when you cant inspect them! although this would mean users may not use --inspect as a switch.