git/list[1] front-page[2] threads[3] people[4] search[5] about
 

[PATCH v2] git-prompt: preserve value of $? inside shell prompt

From
Tony Finch <dot@dotat.at>
Date
Dec 22, 2014, 18:09 UTC
Message-ID
<alpine.LSU.2.00.1412221808110.2546@hermes-1.csi.cam.ac.uk>
In-Reply-To
<xmqqa92fbo0j.fsf@gitster.dls.corp.google.com>

If you have a prompt which displays the command exit status, __git_ps1 without this change corrupts it, although it has the correct value in the parent shell:

	~/src/git (master) 0 $ set | grep ^PS1
	PS1='\w$(__git_ps1) $? \$ '
	~/src/git (master) 0 $ false
	~/src/git (master) 0 $ echo $?
	1
	~/src/git (master) 0 $
There is a slightly ugly workaround:
	~/src/git (master) 0 $ set | grep ^PS1
	PS1='\w$(x=$?; __git_ps1; exit $x) $? \$ '
	~/src/git (master) 0 $ false
	~/src/git (master) 1 $
This change makes the workaround unnecessary.
Signed-off-by: Tony Finch <dot@dotat.at>
---
 contrib/completion/git-prompt.sh | 4 ++++
 1 file changed, 4 insertions(+)
I hope that explains it properly :-)
diff --git a/contrib/completion/git-prompt.sh b/contrib/completion/git-prompt.sh
index c5473dc..5fe69d0 100644
--- a/contrib/completion/git-prompt.sh
+++ b/contrib/completion/git-prompt.sh
@@ -288,6 +288,7 @@ __git_eread ()
 # In this mode you can request colored hints using GIT_PS1_SHOWCOLORHINTS=true
 __git_ps1 ()
 {
+	local exit=$?
 	local pcmode=no
 	local detached=no
 	local ps1pc_start='\u@\h:\w '
@@ -511,4 +512,7 @@ __git_ps1 ()
 	else
 		printf -- "$printf_format" "$gitstring"
 	fi
+
+	# preserve exit status
+	return $exit
 }
-- 
2.2.1.68.g56d9796
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 9 in “git-prompt: preserve command exit status”
  1. git-prompt: preserve command exit statusTony Finch, Dec 22, 2014
  2. Junio C HamanoDec 22, 2014
  3. git-prompt: preserve value of $? inside shell promptTony Finch, Dec 22, 2014
  4. Junio C HamanoDec 22, 2014
  5. Tony FinchDec 22, 2014
  6. SZEDER GáborJan 13, 2015
  7. Tony FinchJan 14, 2015
  8. git-prompt: preserve value of $? in all casesTony Finch, Jan 14, 2015
  9. SZEDER GáborJan 14, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.