Am 23.11.2013 14:18, schrieb Heikki Hokkanen:
> If bash.prompt is set to false, disable the prompt. This is useful
> for huge repositories like the home directory.
> Signed-off-by: Heikki Hokkanen <h...@users.sf.net>
> git-prompt.sh performance seems to be quite bad for big repositories, so
> without a way to disable it selectively for repositories, it becomes unusable
> for people who have their homedir under git. This patch generalizes the
> a bit by allowing the prompt to be disabled by setting bash.prompt to false in
> any repository.
> contrib/completion/git-prompt.sh | 8 ++++++++
> 1 file changed, 8 insertions(+)
> diff --git a/contrib/completion/git-prompt.sh
> index 7b732d2..c982fde 100644
> --- a/contrib/completion/git-prompt.sh
> +++ b/contrib/completion/git-prompt.sh
> @@ -84,6 +84,8 @@
> # GIT_PS1_SHOWCOLORHINTS to a nonempty value. The colors are based on
> # the colored output of "git status -sb" and are available only when
> # using __git_ps1 for PROMPT_COMMAND or precmd.
> +# To disable prompt for a repository, run "git config bash.prompt false"
> # check whether printf supports -v
> @@ -304,6 +306,12 @@ __git_ps1 ()
> + local prompt_setting
> + prompt_setting=$(git config --bool bash.prompt)
> + if [ -n "$prompt_setting" ] && [ "$prompt_setting" == "false" ]; then
> + return
> + fi
Gah! This adds a fork+exec each time the prompt is shown. Not good,
particularly on Windows.
Since your intent is to disable the prompt in the home directory,
wouldn't that mean that most of the time you *don't* want the prompt?
Wouldn't you be better served with a method that *turns on* the prompt?
For example, a shell function that sets PS1 and another one that unsets
it? Or a wrapper that inspects a shell variable and calls __git_ps1 only
when you want a prompt.
> local short_sha
> if [ "$rev_parse_exit_code" = "0" ]; then
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html