diff options
| author | Johannes Altmanninger <aclopte@gmail.com> | 2024-02-25 17:51:13 +0100 |
|---|---|---|
| committer | Maxime Coste <mawww@kakoune.org> | 2024-02-26 19:08:58 +1100 |
| commit | 8a7641284cb6bbc614cd2088f78d6a7f03e49b99 (patch) | |
| tree | 107aef01651f235fdba08f0079f4be754395fe1b /src/shared_string.cc | |
| parent | 03bea7ced428beeda72186eecc50f9a8ce6f4f2b (diff) | |
rc git: hide blame and report error if git blame fails
Similar to the previous patch, when git blame fails it usually means
that the blamed file is not tracked by Git. I don't know of other
common failure scenarios.
Since git blame runs in detached process, failure handling is a bit
more involved. Let's forward stderr to the debug buffer and escalate
the error. I'm not sure how to get the exit code from git blame in
"git blame | perl" - we can't use $PIPESTATUS.
As a workaround, interpret empty output as failure.
In case of failure, also hide blame; this makes the UI more consistent
I think.
Diffstat (limited to 'src/shared_string.cc')
0 files changed, 0 insertions, 0 deletions