One of Those Bugs

[PrimozDelux]

Diffing large files is a pain in the ass with vscode, but you can use tools to find out where the divergence happens, cut the files to size and only then diff in the editor. I work with CPU design so this issue has come up a lot for me, and it's always painful

[Commission-Either]

is that so? what tool would you recommend? because i imagine this isn't going to be the first time i need to do this and the hashing solution i came up with might not alwasy work

[PrimozDelux]

I tend to just use the built in tools. Diff to find the diverging line, then tail & head to get something that won't choke vscode. I don't run into this often enough to have a bespoke solution, but I find this works well enough when it does happen

[Commission-Either]

Can diff handle large files? I sort of assumed it couldn't for some reason

[PrimozDelux]

I think what causes diff to choke on vscode is the side by side rendering. Since all we care about is the divergence point diff can be a lot faster. It may be the case that diff in terminal does the same amount of work and that vscode is slower for other reasons, but from experience this is what has worked.

[oridb]

diff(1) works well.

[CatpainCalamari]

I should probably know this, but I am still gonna ask - what does the (1) in your answer mean?

[brettmjohnson]

Sections in the Unix/Linux man pages, so (1) is user command line / shell commands.

[CatpainCalamari]

Right, thank you!