Re: default aliases (ci, di, st, co)
On Thu, Jul 09, 2009 at 09:00:30AM +0200, Andreas Ericsson wrote:
Show 23 quoted lines
> Ondrej Certik wrote:
> > Hi,
> > coming to git from mercurial and svn, here is the alias part of my
> > .gitconfig:
> > [alias]
> > ci = commit
> > di = diff --color-words
> > st = status
> > co = checkout
> > And all is fine until I share commands to checkout my branch (for
> > example) with other people, then basically I have to write those
> > commands in full (e.g. commit, checkout, ...), since I cannot assume
> > they have their .gitconfig setup the same way I do. Especially for
> > people who are new to git.
> > What is the view on this in the git community?
>
>
> Personally I think "plain" aliases like you use above are evil.
> git is not svn or mercurial. If you use it like svn you'll be
> surprised sooner or later and your workflow will feel awkward or
> just plain wrong. hg and git are very similar, but the fact that
> hg assumed the svn shorthands implies to me that they've tried
> to retain a compatibility that does not, in fact, exist.
No, it just means that shorting common commands is useful and common.
> I have no simple aliases for any of the commands. There's just no reason
> for them since tab completion works so well.
"Intelligent" bash completion always gets in my way, so I can't use it.
I vote yes.
--
Luciano Rocha <luciano@eurotux.com>
Eurotux Informática, S.A. <http://www.eurotux.com/>