Thread (3 messages) flat view 3 messages, 2 authors, 2016-06-15

Re: git-prompt.sh vs leading white space in __git_ps1()::printf_format

From: Simon Oosthoek <hidden>
Date: 2016-06-15 22:55:27

On 28/11/12 21:47, Junio C Hamano wrote:
Simon Oosthoek [off-list ref] writes:
quoted
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?
Looks better than my suggestion :-)

thanks

/Simon
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help