Re: [PATCH] Move all dashed form git commands to libexecdir

From: Steffen Prohaska <prohaska@zib.de>
Date: Nov 30, 2007, 05:51 UTC
Message-ID: <5E2A9E2B-8B9A-46B0-99D0-DB3798F10119@zib.de>
In-Reply-To: <alpine.LFD.0.9999.0711291821220.8458@woody.linux-foundation.org>

On Nov 30, 2007, at 3:29 AM, Linus Torvalds wrote:

Show 19 quoted lines

> So I just think that the whole idiotic complaint that some people have
> (that whole "git-<tab><tab>" shows "Display all 144 possibilities?"  
> and
> people are somehow using that as an argument that git is "complex")  
> should
> be something we strive to undo. I think the complaint is insane  
> (because
> the answer is "well, nobody forces you to _use_ all the power and  
> scripts
> we give you!"), but still, it's a complaint, so let's just assume  
> the user
> is right, and try to fix it.
>
> So when you do "git-<tab><tab>" it should just beep at you and not  
> show
> anything at all by default. And when you do "git <tab><tab>", we  
> should
> make sure that the bash expansion (or zsh or whatever) shows a nice
> collection of common plumbing, not soemthing really scary.

What will happen to gitk?

Shouldn't it be included in the nice collection? gitk is an essential command. Then, following your reasoning, "git <tab><tab>" should recommend it, no?

Note, "git gui" already works. gitk would really be the last git "command" that can't be accessed through "git <command>"

	Steffen