On Thu, Mar 18, 2010 at 2:06 AM, David Aguilar <davvid@gmail.com> wrote:
quoted text
> You caught my attention.  I don't personally like csh.  In fact,
> I'm actively working on a way to get us off of csh here at
> $dayjob.  Hence, I usually shy away from anything that
> encourages csh usage.
>
> That said, I'm a practical person.  We've written a
> git-completion.tcsh here so I figured I'd share.
>
> Caveats -- it sucks!  I'm pretty sure that this is due
> to either a) csh's poor completion facilities, or b) my
> inability to use it to its best ability.  The thing that really
> kills me is that I can't figure out how to get both path
> completion and --option completion at the same time.
> For a while I had 'echo *' in there to handle that but
> that breaks down once you start completing down a subdirectory
> (the "/" breaks it).  Hence, we always use the '--' separator
> when specifying pathspecs.

But it works, from a user point of view.

quoted text
> What I learned from this exercise?
> Bash completion is effin amazing!  (typed from a bash terminal)
>
> I'm sure there's plenty of ways to improve this.  Aside from
> throwing it in contrib/ and hoping others find it useful enough
> to improve it, I've probably hit my tcsh completion-foo limit.

I'll put it in my ~/.tcsh and see how it goes. Thanks.
-- 
Duy
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html