when working on large files with long histories, git blame can take a long time (on the order of tens of minutes for especially bad ones). to prove that it's not stalling and to give you a ballpark of remaining time, git provides a git blame --progress flag to show you a little summary of progress. currently, :Git blame --progress appears to behave no differently than without the flag; but it would be neat if the little progress thing could be shown on screen like how fidget does.
is this already living somewhere that I should be connecting to for fidget to consume on my end or could this be something that fugitive shows?
when working on large files with long histories,
git blamecan take a long time (on the order of tens of minutes for especially bad ones). to prove that it's not stalling and to give you a ballpark of remaining time, git provides agit blame --progressflag to show you a little summary of progress. currently,:Git blame --progressappears to behave no differently than without the flag; but it would be neat if the little progress thing could be shown on screen like how fidget does.is this already living somewhere that I should be connecting to for fidget to consume on my end or could this be something that fugitive shows?