Re: [PATCH] Improve bash prompt to detect various states like an unfinished merge

2 messages, 2 authors, 2016-06-15 · open the first message on its own page

Re: [PATCH] Improve bash prompt to detect various states like an unfinished merge

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:43:37

Robin Rosenberg [off-list ref] writes:
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.
Since you show the name of the branch anyway, I have to wonder
why you should say BISECT.

Also if you know you normally get branch name, lack of branch
name would indicate detached HEAD, I would presume.

But other state information may be helpful.

Re: [PATCH] Improve bash prompt to detect various states like an unfinished merge

From: Robin Rosenberg <hidden>
Date: 2016-06-15 22:43:37

måndag 01 oktober 2007 skrev Junio C Hamano:
Robin Rosenberg [off-list ref] writes:
quoted
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.
Since you show the name of the branch anyway, I have to wonder
why you should say BISECT.
You can wonder around different branches while bisecting. The BISECT
part is there to remind you that you are already doing bisecting, especially
when being away from the prompt for a while. I did some mistakes without it.
Also if you know you normally get branch name, lack of branch
name would indicate detached HEAD, I would presume.
Yes, sure, but I like it better this way.
But other state information may be helpful.
This is an example script, so I'd say it's better to have a little too much 
and let people remve stuff they don't like in their personal copies.

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