Support external diff algorithms in internal diff editor
Reopening closed feature request #30694 Openness, extensibility and customisability are the features that keep me coming back to VSCode. Being built upon an OSS core (Electron) was strong evidence of a change of culture at Microsoft. In that spirit, would you please reconsider the original request from @myfairsyer. Different diffing algorithms produce [significantly different results][1] and are suited to different purposes. There is no one-size-fits-all solution. Paraphrasing @myfairsyer, **please consider abstracting the diff functionality to allow different *hunk-list providers***. Respecting [the algorithm set in Git configuration][2] would be an ideal baseline. As another example, **BeyondCompare** allows [significant customisation][3], including 2 of the 4 algorithms offered by Git. [1]: https://link.springer.com/article/10.1007/s10664-019-09772-z [2]: https://git-scm.com/docs/git-diff#Documentation/git-diff.txt---diff-algorithmpatienceminimalhistogrammyers [3]: https://www.scootersoftware.com/v4help/index.html?sessiontextalignment.html
Posted by pvspain on Nov 17, 2019, 4:43 AM
Tags
Related issues
- some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
- I think of this as the kiosk economy.
- What a goofy comment.
- There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
- Compose support in WSLc
- [RFC] Roadmap to v2.0
Raise real-world problems, find people facing the same issue, and discuss solutions.3,500 issues0 comments
support (Other)
some bike vendor told me that the biggest problem with regular to ebike conversion was that regular bike frames were not strong enough to...
I think of this as the kiosk economy.
What a goofy comment.
There's lots of evidence for positive influences of Caffeine on the body (some negative as well), especially the brain.
Compose support in WSLc
[RFC] Roadmap to v2.0
[Feature]: Add TurboQuant Support for KV Cache Quantization
Support for AGENTS.md and .agents/skills/, the community has been asking since August 2025
Support external diff algorithms in internal diff editor
Reopening closed feature request #30694 Openness, extensibility and customisability are the features that keep me coming back to VSCode. Being built upon an OSS core (Electron) was strong evidence of a change of culture at Microsoft. In that spirit, would you please reconsider the original request from @myfairsyer. Different diffing algorithms produce [significantly different results][1] and are suited to different purposes. There is no one-size-fits-all solution. Paraphrasing @myfairsyer, **please consider abstracting the diff functionality to allow different *hunk-list providers***. Respecting [the algorithm set in Git configuration][2] would be an ideal baseline. As another example, **BeyondCompare** allows [significant customisation][3], including 2 of the 4 algorithms offered by Git. [1]: https://link.springer.com/article/10.1007/s10664-019-09772-z [2]: https://git-scm.com/docs/git-diff#Documentation/git-diff.txt---diff-algorithmpatienceminimalhistogrammyers [3]: https://www.scootersoftware.com/v4help/index.html?sessiontextalignment.html
Comments (0)
No comments yet. Start the discussion.