it's only accurate when the buffer is in saved state. Check out\r
`diff-hl-flydiff-mode`, it aims to handle unsaved buffers as well.\r
\r
+* To use an\r
+ [alternative diff algorithm](http://stackoverflow.com/questions/32365271/whats-the-difference-between-git-diff-patience-and-git-diff-histogram)\r
+ with Git, add a corresponding argument to `vc-git-diff-switches`,\r
+ e.g. `(setq vc-git-diff-switches '("--histogram"))`. Using the\r
+ `diff.algorithm` option doesn't work\r
+ [because](http://article.gmane.org/gmane.comp.version-control.git/294622)\r
+ `vc-git-diff` calls `git diff-index`. `diff-hl-flydiff-mode` does\r
+ not support alternative algorithms, because it uses the external\r
+ `diff` program.\r
+\r
* We conflict with other modes when they put indicators on the fringe,\r
such as [Flycheck](https://github.com/flycheck/flycheck). This is\r
rarely a significant problem, since if you're using such a mode,\r
Magit\r
-----\r
\r
-If you have a recent enough version installed, it defines\r
-`magit-revert-buffer-hook` (or `magit-not-reverted-hook`), which we use.\r
+If you're using a version before 2.4.0, it defines `magit-revert-buffer-hook`\r
+(or `magit-not-reverted-hook`), which we use.\r
+\r
+When using Magit 2.4 or newer, add this to your init script:\r
+\r
+```lisp\r
+(add-hook 'magit-post-refresh-hook 'diff-hl-magit-post-refresh)\r
+```\r