From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: David Aguilar <davvid@gmail.com>
Cc: Jay Soffian <jaysoffian@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: git branch --current?
Date: Thu, 18 Mar 2010 09:00:45 +0700 [thread overview]
Message-ID: <fcaeb9bf1003171900i261068d2m954cbc22499b1b07@mail.gmail.com> (raw)
In-Reply-To: <20100317190645.GA8304@gmail.com>
On Thu, Mar 18, 2010 at 2:06 AM, David Aguilar <davvid@gmail.com> wrote:
> 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.
> 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
prev parent reply other threads:[~2010-03-18 2:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-17 14:43 git branch --current? Nguyen Thai Ngoc Duy
2010-03-17 14:48 ` Jay Soffian
2010-03-17 15:04 ` Nguyen Thai Ngoc Duy
2010-03-17 15:14 ` Jay Soffian
2010-03-17 19:06 ` David Aguilar
2010-03-18 2:00 ` Nguyen Thai Ngoc Duy [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fcaeb9bf1003171900i261068d2m954cbc22499b1b07@mail.gmail.com \
--to=pclouds@gmail.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=jaysoffian@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).