Nicolas Pitre wrote:
On Fri, 15 Dec 2006, Andreas Ericsson wrote:
Nicolas Pitre wrote:
On Fri, 15 Dec 2006, Jakub Narebski wrote:
It would be nice to have some generic place in git config to specify
default options to git commands (at least for interactive shell). It
cannot be done using aliases. Perhaps defaults.<command> config variable?
I would say the alias facility has to be fixed then.
In bash you can alias "ls" to "ls -l" and it just works.
I think this is because git scripts that need a certain git command to work a
certain way don't want some alias to kick in and destroy things for them.
Shell-scripts would have the same problem if you alias "awk" to "grep" f.e.,
which is why prudent shell-scripters use the "unalias -a" thing.
Wouldn't it be possible for aliases to be effective only when issued
from an interactive shell? It is certainly true that aliases just make
no sense in a script.
Yes, but then aliases wouldn't work in one-liners, which would be a bit
of a shame and pretty likely to cause some "interesting" bugreports.
Perhaps an environment variable GIT_IGNORE_ALIAS=yes that git-scripts
can set at the beginning of execution?
--
Andreas Ericsson andreas.ericsson@xxxxxx
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html