From: "Shawn O. Pearce" <spearce@spearce.org>
To: Marcus Griep <marcus@griep.us>
Cc: Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>,
Jonathan Nieder <jrnieder@uchicago.edu>
Subject: Re: [PATCH v2] bash-completion: Add non-command git help files to bash-completion
Date: Fri, 15 Aug 2008 11:00:59 -0700 [thread overview]
Message-ID: <20080815180059.GA17399@spearce.org> (raw)
In-Reply-To: <1218823168-1753-1-git-send-email-marcus@griep.us>
Marcus Griep <marcus@griep.us> wrote:
> Git allows access to the gitattributes man page via `git help attributes`,
> but this is not discoverable via the bash-completion mechanism. This
> patch adds all current non-command man pages to the completion candidate
> list.
>
> Signed-off-by: Marcus Griep <marcus@griep.us>
Acked-by: Shawn O. Pearce <spearce@spearce.org>
> diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> index c0bf7aa..158b912 100755
> --- a/contrib/completion/git-completion.bash
> +++ b/contrib/completion/git-completion.bash
> @@ -885,7 +885,11 @@ _git_help ()
> return
> ;;
> esac
> - __gitcomp "$(__git_all_commands)"
> + __gitcomp "$(__git_all_commands)
> + attributes cli core-tutorial cvs-migration
> + diffcore gitk glossary hooks ignore modules
> + repository-layout tutorial tutorial-2
> + "
> }
>
> _git_init ()
--
Shawn.
next prev parent reply other threads:[~2008-08-15 18:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 16:15 [PATCH] bash-completion: Add non-command git help files to bash-completion Marcus Griep
2008-08-15 17:38 ` Jonathan Nieder
2008-08-15 17:53 ` Marcus Griep
2008-08-15 17:59 ` [PATCH v2] " Marcus Griep
2008-08-15 18:00 ` Shawn O. Pearce [this message]
2008-08-16 9:30 ` Junio C Hamano
2008-08-15 18:21 ` [PATCH] " Junio C Hamano
2008-08-15 18:33 ` Marcus Griep
2008-08-15 18:50 ` Junio C Hamano
2008-08-15 19:03 ` Marcus Griep
2008-08-15 20:32 ` Pieter de Bie
2008-08-15 21:17 ` Marcus Griep
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=20080815180059.GA17399@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@uchicago.edu \
--cc=marcus@griep.us \
/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.