From: Junio C Hamano <gitster@pobox.com>
Date: Wed, 28 Nov 2012 20:47:16 GMT
Subject: Re: git-prompt.sh vs leading white space in __git_ps1()::printf_format
Message-ID: <7vlidltpyj.fsf@alter.siamese.dyndns.org>
In-Reply-To: <50B66F41.1030305@xs4all.nl>

Simon Oosthoek <s.oosthoek@xs4all.nl> writes:

> perhaps the point should read like this:
> #    3a) In ~/.bashrc set PROMPT_COMMAND
> #        To customize the prompt, provide start/end arguments
> #        PROMPT_COMMAND='__git_ps1 "\u@\h:\w" "\\\$ "'
>
> Which would not be confusing at all, I think...

It says "to customize", so a user who just wants the default (which
does not exist but the comment does not say so) would be left
without instruction, no?

    In $HOME/.bashrc, PROMPT_COMMAND can be set to
    '__git_ps1 <pre> <post>', where <pre> and <post>
    are strings you would put in $PS1 before and after
    the status string generated by git-prompt machinery.
    e.g.
        PROMPT_COMMAND='__git_ps1 "\u@\h:\w" "\\\$ "'

or something?