git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Visher <tim.visher@gmail.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Thoughts on git-completion
Date: Mon, 1 Mar 2010 15:34:47 -0500	[thread overview]
Message-ID: <c115fd3c1003011234m75df37ehed54a59552f681a5@mail.gmail.com> (raw)
In-Reply-To: <20100301195751.GG24776@spearce.org>

On Mon, Mar 1, 2010 at 2:57 PM, Shawn O. Pearce <spearce@spearce.org> wrote:
> Tim Visher <tim.visher@gmail.com> wrote:
>> I `alias g=git` and `alias gk=gitk` on every machine that I use git on
>> and I have to edit the git-completion.bash script in order to get the
>> marvelous completion provided by that script with my aliases.  Is this
>> something that could be rolled in to the official release or does this
>> rest firmly in the personal customization realm?  I'm prepared to
>> submit a patch if you'd like.
>
> Does adding to your local script
>
>  complete -o bashdefault -o default -o nospace -F _git g 2>/dev/null \
>  || complete -o default -o nospace -F _git g
>
> work for you?  It seems to me you just need to tell bash to run
> _git or _gitk when doing completion for your alias.

The patch that I use is:

    2290a2291,2295
    > complete -o bashdefault -o default -o nospace -F _git g 2>/dev/null \
    >        || complete -o default -o nospace -F _git g
    > complete -o bashdefault -o default -o nospace -F _gitk gk 2>/dev/null \
    >        || complete -o default -o nospace -F _gitk gk

-- 

In Christ,

Timmy V.

http://burningones.com/
http://five.sentenc.es/ - Spend less time on e-mail

      reply	other threads:[~2010-03-01 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-01 19:51 Thoughts on git-completion Tim Visher
2010-03-01 19:57 ` Shawn O. Pearce
2010-03-01 20:34   ` Tim Visher [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=c115fd3c1003011234m75df37ehed54a59552f681a5@mail.gmail.com \
    --to=tim.visher@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=spearce@spearce.org \
    /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).