Re:Display your current git branch as part of your bash prompt
by decklin on Sunday August 16, 2009 @11:25PM
(#767279)
Personally, I'd argue you do want to keep track of whether you are in a repo or not, since including that pipeline in your PS1 always forks three processes on every prompt. And if you're going to do that in your shell, it's good to have separate commands for each task.
For the case of not being on a branch, the output of 'git branch' is not very useful. I am currently using 'git name-rev --name-only HEAD', but the contrib script has an even fancier mechanism (via 'git describe') for coming up with something to display when HEAD isn't a symbolic ref.
Re:Display your current git branch as part of your bash prompt
by davidmathers on Monday August 17, 2009 @12:07AM
(#767336)
Try this:
export PS1='\w:$(__git_ps1 "%s")$ '
function parse_git_dirty {
git diff --quiet HEAD &>/dev/null
[[ $? == 1 ]] && echo "✎ " || echo "➜ "
}
function parse_git_branch {
local branch=$(__git_ps1 "%s")
[[ $branch ]] && echo "$branch$(parse_git_dirty)"
}
PS1='\u@\h $(parse_git_branch)\W $ '
Had I known about `git symbolic-ref`, I might have used that instead of `git branch`. On the other hand, I would have needed to re-implement lots of what `git branch` does, such as detecting the difference between not being in a git repository and simply not being on a branch.
The interface of `git branch` seems stable enough that I doubt it will break this. If it does, it should take me no longer than 5 minutes to fix, since that's about how long it would take me to re-write the whole thing from scratch.
Is there any particular reason that using `git symbolic-ref` is better than `git branch` in this case, given that I want human-readable output, instead an unambiguous filesystem location?