From: Shawn Pearce <spearce@spearce.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Contributed bash completion support for core Git tools.
Date: Mon, 18 Sep 2006 13:29:58 -0400 [thread overview]
Message-ID: <20060918172958.GB31140@spearce.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0609181012180.19042@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> the only gripe I have with it: whenever some options are added, or
> removed, or renamed, you have to adapt the completion script. That is why
> I started (ages ago) to auto-generate the completion script from the
> documentation (of course, this means that the options have to be described
> consistently in the documentation, which is good in its own).
>
> Unfortunately, I never got around to finish it, but a preliminary version
> is in the mailing list archives.
I was torn about putting options into the completion list. Right now
"-l -b -f" are available for 'git checkout' but I think that was
a bad idea. There's little point in offering completion for an
option which is a single character. But that's my opinion and I'm
sure someone else might actually find it useful.
Longer options however such as "--since" or "--pretty=" with its
associated format options, or the merge strategy argument to "-s"
would all be nice to have completion support for. However I did
not implement these.
> However, since your script works well, and I do not have a working script,
> you clearly won! So, unless some kind soul actually implements my
> proposal, I am happy with your script.
I was mainly getting tired of copying and pasting or retyping
branch names and remote names. So that's what I implemented.
(And remote names aren't quite right as they don't tab complete
the ones available in .git/config.)
--
Shawn.
next prev parent reply other threads:[~2006-09-18 17:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-18 0:48 [PATCH] Contributed bash completion support for core Git tools Shawn Pearce
2006-09-18 1:03 ` Junio C Hamano
2006-09-18 1:18 ` Shawn Pearce
2006-09-28 16:16 ` Junio C Hamano
2006-09-28 16:28 ` Shawn Pearce
2006-09-18 8:17 ` Johannes Schindelin
2006-09-18 17:29 ` Shawn Pearce [this message]
2006-09-18 8:23 ` Junio C Hamano
2006-09-18 17:42 ` Shawn Pearce
2006-09-18 8:31 ` Sebastian Harl
2006-09-18 17:55 ` Shawn Pearce
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=20060918172958.GB31140@spearce.org \
--to=spearce@spearce.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.