Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

The one thing I don't think bash aliases give you is proper handling of nested subcommands. Can you easily do "juju st" in a bash alias? or does it have to become "juju-st" ? I think the caveats around people aliasing their way out of clumsiness in the tool is actually something to pay close

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

You can accomplish most of this with the existing plugin system. You can't override existing commands, but you can easily create thin wrappers around them with your desired default args, and given the discussion around --no-aliases, it seems like this is actually a benefit. And plugins provide

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

I can't help but draw parallels to the plugin system. There was considerable resistance to adding the ideas of plugins to Juju. It was added complexity that no one needed and could be done simply using existing executable scripts, like juju-foo. Tim On 28/10/15 07:33, Cory Johns wrote: > You

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Thank you! Aaron On 2015-10-26 09:22 PM, Tim Penhey wrote: > On 24/10/15 04:05, Aaron Bentley wrote: >> bzr has a similar feature, but the problem with such a feature is >> that it can break scripts that expect the normal behaviour. >> That's why

Re: New feature for 1.26 (master), $(JUJU_HOME)/aliases

You're not selling me on this ;) On Tue, Oct 27, 2015, 4:01 PM Tim Penhey wrote: > I can't help but draw parallels to the plugin system. > > There was considerable resistance to adding the ideas of plugins to > Juju. It was added complexity that no one needed and