Re: [PATCH] Improve bash prompt to detect merge / rebase in progress
- From
Robin Rosenberg <robin.rosenberg@dewire.com>
- Date
- Sep 1, 2007, 23:52 UTC
- Message-ID
- <200709020152.30070.robin.rosenberg@dewire.com>
- In-Reply-To
- <7vir6us1ia.fsf@gitster.siamese.dyndns.org>
lördag 01 september 2007 skrev Junio C Hamano:
Show 27 quoted lines
> Robin Rosenberg <robin.rosenberg@dewire.com> writes:
>
> > diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash
> > index 5ed1821..1fef857 100755
> > --- a/contrib/completion/git-completion.bash
> > +++ b/contrib/completion/git-completion.bash
> > @@ -64,12 +64,34 @@ __gitdir ()
> >
> > __git_ps1 ()
> > {
> > - local b="$(git symbolic-ref HEAD 2>/dev/null)"
> > - if [ -n "$b" ]; then
> > + local g="$(git rev-parse --git-dir 2>/dev/null)"
> > + if [ -n "$g" ]; then
> > + local r
> > + local b
> > + if [ -d "$g/../.dotest" ]
> > + then
> > + local b="$(git symbolic-ref HEAD 2>/dev/null)"
> > + r="|REBASEING"
>
> I might be in the middle of resolving a conflicted "git am".
>
> But I love the idea. We need to think about cleaning up our
> "state machine" mechanism to make this kind of thing easier to
> do. We've had a few suggestions on the list in the past but
> they never passed the suggestion/speculation stage.I'd love to see that. The Eclipse plugin needs to know about such things in order to prevent the user from making errors he wouldn't like to do. We do commit and checkouts without looking for these states now. Not too good.
The downside of improving the state machine is that we'll have to detect the old AND the new states.
Here's an ever better version which handles bisect and detached heads.
-- robin
From e5b2b9833786f13d729b7fead74297580b03f775 Mon Sep 17 00:00:00 2001 From: Robin Rosenberg <robin.rosenberg@dewire.com> Date: Sat, 1 Sep 2007 12:20:48 +0200 Subject: [PATCH] Improve bash prompt to detect various states like an unfinished merge
This patch makes the git prompt (when enabled) show if a merge or a rebase is unfinished. It also detects if a bisect is being done as well as detached checkouts.
An uncompleted git-am cannot be distinguised from a rebase (the non-interactive version). Instead of having an even longer prompt we simply ignore that and hope the power users that use git-am knows the difference.
Signed-off-by: Robin Rosenberg <robin.rosenberg@dewire.com> --- contrib/completion/git-completion.bash | 37 ++++++++++++++++++++++++++++--- 1 files changed, 33 insertions(+), 4 deletions(-)
diff --git a/contrib/completion/git-completion.bash b/contrib/completion/git-completion.bash index 5ed1821..048a715 100755 --- a/contrib/completion/git-completion.bash +++ b/contrib/completion/git-completion.bash @@ -64,12 +64,41 @@ __gitdir () __git_ps1 () { - local b="$(git symbolic-ref HEAD 2>/dev/null)" - if [ -n "$b" ]; then + local g="$(git rev-parse --git-dir 2>/dev/null)" + if [ -n "$g" ]; then + local r + local b + if [ -d "$g/../.dotest" ] + then + local b="$(git symbolic-ref HEAD 2>/dev/null)" + r="|REBASING" + else + if [ -d "$g/.dotest-merge" ] + then + r="|REBASING" + b="$(cat $g/.dotest-merge/head-name)" + else + if [ -f "$g/MERGE_HEAD" ] + then + r="|MERGING" + b="$(git symbolic-ref HEAD 2>/dev/null)" + else + if [ -f $g/BISECT_LOG ] + then + r="|BISECTING" + fi + if ! b="$(git symbolic-ref HEAD 2>/dev/null)" + then + b="$(cut -c1-7 $g/HEAD)..." + fi + fi + fi + fi + if [ -n "$1" ]; then - printf "$1" "${b##refs/heads/}" + printf "$1" "${b##refs/heads/}$r" else - printf " (%s)" "${b##refs/heads/}" + printf " (%s)" "${b##refs/heads/}$r" fi fi }
-- 1.5.3.rc7.844.gfd3c5