diff options
author | Tom Ryder <tom@sanctum.geek.nz> | 2016-12-27 02:41:56 +1300 |
---|---|---|
committer | Tom Ryder <tom@sanctum.geek.nz> | 2016-12-27 02:41:56 +1300 |
commit | d71d8492a373306333711da74c3318f9c2c67d53 (patch) | |
tree | cce10030688de84dcec1d0e3509a4f6ce552c0d9 | |
parent | Tell ShellCheck to ignore an error (diff) | |
download | dotfiles-d71d8492a373306333711da74c3318f9c2c67d53.tar.gz dotfiles-d71d8492a373306333711da74c3318f9c2c67d53.zip |
Add workaround to what looks like a bug to me
-rw-r--r-- | ISSUES.markdown | 4 | ||||
-rw-r--r-- | bash/bashrc.d/prompt.bash | 5 |
2 files changed, 9 insertions, 0 deletions
diff --git a/ISSUES.markdown b/ISSUES.markdown index 60558e80..5d9d43d3 100644 --- a/ISSUES.markdown +++ b/ISSUES.markdown @@ -20,3 +20,7 @@ Known issues manageable * On non-OBSD pdksh and mksh, !! comes out as literal !! after subshell expansion; a version switch might be necessary +* Running the block of git(1) commands in the prompt leaves five "stale" + jobspecs around that flee after a jobs builtin run; only saw this manifest + after 90dcadf; either I understand job specs really poorly or this may be a + bug in bash diff --git a/bash/bashrc.d/prompt.bash b/bash/bashrc.d/prompt.bash index aa96cdda..123c4146 100644 --- a/bash/bashrc.d/prompt.bash +++ b/bash/bashrc.d/prompt.bash @@ -156,6 +156,11 @@ prompt() { } >/dev/null 2>&1 + # For some reason, five commands in the above block seem to stick + # around as jobs after this command is over; I don't know why, but + # this clears it; might be a bug + jobs >/dev/null + # Print the status in brackets; add a git: prefix only if there # might be another VCS prompt (because PROMPT_VCS is set) printf '(%s%s%s%s)' \ |