Typing v in Magit Diff mode causes an often slow and uncecessary refresh. Can this be avoided?

For example when looking at a diff between a range of commits (say origin/mater...HEAD). Typing v (A.K.A. M-x magit-revert-no-commit) applies the reversed hunk to the worktree. The diff between the commits has not changed, but Magit still refreshes the entire buffer. Even if the diff does change, I often would still like to avoid refreshes when I have large diffs that take minutes to refresh.

1 Answer 1


No, unfortunately Magit isn't smart enough to notice that there's no need to refresh (and there is not setting to just suppress refreshing altogether). I plan to implement intelligent refresh one day™ but better don't hold your breath.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.