Currently, the core generate command usage pattern is
completely generate [CONFIG_PATH OUTPUT_PATH]
If we wish to install at generation time, then there is no point in having OUTPUT_PATH.
My proposal is to change the pattern to
completely generate [CONFIG_PATH OUTPUT]
Where OUTPUT can be:
- a path = same behavior as the live one
- a hyphen = output to stdout, already implemented for 0.7.3
- a command name prefixed by
@ - for exampe, @mycli = this will install it for this command
This will allow acrobatics like this:
some_config_generator | completely generate - @mycli
If anyone (@christerswahn) has thoughts or concerns, please comment.
Currently, the core generate command usage pattern is
If we wish to install at generation time, then there is no point in having
OUTPUT_PATH.My proposal is to change the pattern to
Where OUTPUT can be:
@- for exampe,@mycli= this will install it for this commandThis will allow acrobatics like this:
If anyone (@christerswahn) has thoughts or concerns, please comment.