I use text diff utilities at work all the time. BC3 is really hard to beat. Gap is some attempt to create the BC3 magic.
I use text diff utilities at work all the time. BC3 is really hard to beat. Gap is some attempt to create the BC3 magic.
When I said this was the last update to &gap , I wasn't lying, but I do have one other thing I'd like to share... gap is also open source! https://github.com/cdacamar/gap
Why is this interesting? gap is using much of the same tech that fred is built on: custom OS layers, renderers, arenas, etc. If you're curious about how I write HM C++ or just generally curious about some of the bones behind fred, feel free to take a look!
Note: the base layers are older snapshots of what is currently in fred.
One final update to &gap . As one more handy feature for usability, I added the ability to drag-and-drop files onto a specific diff-side to retarget that side. If you need to compare the left-hand side to another file on disk, its as easy as grabbing and dragging the new compare target onto the right-hand side.
And just like I was hoping for when I started &gap , I can now use it for git diff when viewing local repo changes!
Making diffs more intuitive was the work item for today. VSCode, Azure DevOps, etc. have their own diff algorithm that does some pretty useful stuff to help guide the reader into context. This change to &gap helps to provide even more visibility into inner-diffs by offering a word-based or character-based inner-diff. Sometimes one or the other can help you see changes a little bit better.
First image: word-based inner-diff.
Second image: character-based inner-diff.
I added context window narrowing to &gap . This is very helpful for skipping large common areas in bigger files.
A lot more functionality hooked up including the, annoyingly difficult to implement, sub-diff regions. &gap
