This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| # snip .bashrc | |
| function bash_git_branch | |
| { | |
| git branch 2> /dev/null | grep \* | python -c "print '['+raw_input()[2:]+']'" 2> /dev/null | |
| } | |
| #snip .bashrc | |
| PS1='${debian_chroot:+($debian_chroot)}\u@\h:\w$(bash_git_branch)\$ ' | |
| #snip the rest |
This will show up a prompt which looks like this and fails gracefully when you are not on a git repo.
vagmi@deepthought:~/work/testproj[master]$ git checkout new_feature
Switched to branch "new_feature"
vagmi@deepthought:~/work/testproj[new_feature]$ cd ..
vagmi@deepthought:~/work$
This saves a lot of "git branch" when you are coding.
6 comments:
the stuff in your pre tag didn't come in the google reader.. and i banged my head for couple of seconds.. wonder if the github thing is worth it
May be I should just post the code snippet directly on the blog instead of putting it as a gist. But the gist formatting is so pretty. :-)
Well it works absolutely fine!
Ah, nice idea, thanks.
I added it to my "setup my coding environment" script, using this line:
export PS1=`echo "$PS1"|sed -r s/\(.*\\w\)\(.*\)/\\\\1\$\(bash_git_branch\)\\\\2/`
Nice idea, but invoking python on each prompt is a bit overkill, here's a lighter implementation:
git branch 2>/dev/null | sed -ne 's/^\* \(.*\)//p'
How about awk?
function bash_git_branch
{
git branch 2> /dev/null | grep \* | awk '{print $2}'
}
Post a Comment