Handle new output from git blame command when using --contents
gunslingerfry opened this issue · comments
Matthew Fry commented
Starting with git 2.4.1, using --contents git outputs "External file (--contents)" instead of "Not committed yet." This is an extremely bizarre decision because the command doesn't know the current state of the file on disk and therefore it cannot differentiate between change that are truly 'not committed yet' and ones that are just in the temporary buffer passed in.
This breaks all 'real time' git blame plugins like coc-git. coc-git should mitigate this change by replacing the output "External file (--contents)" with the previous message "Not committed yet."
Here is the commit of limited usefulness from git:
git/git@603d0fd