Re: allowing aliases to override builtins to support default options
- From
Jay Soffian <jaysoffian@gmail.com>
- Date
- Mar 7, 2009, 02:57 UTC
- Message-ID
- <76718490903061857y5446098by3633559697508c2e@mail.gmail.com>
- In-Reply-To
- <alpine.DEB.1.00.0903070336200.10279@pacific.mpi-cbg.de>
On Fri, Mar 6, 2009 at 9:37 PM, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> What you dream about breaks a lot of scripts.
I said I understood the implications.
> So while it might be nice for you, you would make life of others much, > much, much harder. Not nice at all.
This is not something I am dreaming about, and I'm only interested to the extent that it improves git w/o hindering existing users. I'm certainly not aiming to be not nice to anyone!
For example, what if:
1. The aliases applied only to porcelain commands, not to plumbing. 2. The aliases worked only if stdout was a terminal, using the same method that git uses for detecting when it is okay to start a pager. 3. git took --alias-builtins and --no-alias-builtins just like it takes --paginate and --no-pager to override (2).
j.