Annoying 'Changes are too large to display' message

[DaanConn]

Sometimes I get this message when I want to display my changes in a source file. I then can only press a button 'Load Diff' and the changes are shown correctly. However, there are not many changes at all, this message even pops up if 1 character is added with respect to the previous version of the file.

It's quite annoying, since the message is shown every time when I want to see the changes.

The only thing I can imagine why this message pops up, is because the source file contains rather long lines (195 chars) since it is a generated file...

Can this message be removed somehow?

[marcpeterson]

I find this annoying too. The "show entire file" button will sometimes make the entire file appear (you'll need to click "load diff" again after toggling).

It would still be nice to have a setting to turn this off, or allow us to set how many lines would trigger the condensed view.

[rmarskell]

This is my one gripe with Fork. I have a file with a single line added to it and "Changes are too large to display" seemingly because of the file size. This happens to me daily. I would like the ability to turn this off or, even better, specify the limit values.

[simonvanbernem]

I added a file with 3000 characters on one line and also got the "Changes are too large to Display" message. No biggy, really, but just wanted to mention that this is not the behaviour I would have expected, especially since the diff with word-wrap active is only about 10 lines.

[DanPristupov]

I added a file with 3000 characters on one line

Minimised changes are very bad handled by text controls. At the time those controls were developed, there were no minimised source code and that case is not optimised.

[lhaeger]

Still an issue, I only see it on Windows btw. not on my Mac. This one has 67 lines, 31kB file size:

[B-iggy]

@DanPristupov any news on this please?
Please implement at least an option to remove your button "Load Diff" and show us whatever there might come or not come. (most of the time it's bugged anyways and only few lines are changed but you claim it as "changes are too large")

[BeigeBadger]

+1 to the above.

I've started running into this recently, and it's really annoying.

[adams13x13]

I get this message with a file that is 18 kB small. After pushing the “Load Diff” button, the diff window comes instantly, but it takes much longer to click “Load Diff” for every file. I have checked with Fork 1.89.1.0.

Please at least increase the size limit to some value that a moderate computer can handle.

[gaspardpetit]

A setting to set the maximum diff size would certainly be useful. This value will change over the years and depending on the hardware. On most of the file I have that requires a manual "Load Diff", the diff loads in the blink of an eye - so definitely not too big.

[ronnieshipman]

I see this bug too in Fork v1.94.1.0.
@DanPristupov I can (privately) email you example files if you like. I have files with very similar content, sizes and file lengths, where one exhibits this problem and the other does not.

[DanPristupov]

@ronnieshipman does the file have long lines?

[ronnieshipman]

@DanPristupov They both have long lines. The longest line in the file exhibiting this problem is 2075 columns (file size approx 142k) . The longest line in the file that does not have this issue is 1461 columns (file sizes approx 146k). I use the term columns instead of chars because there are tabs at the beginning of almost every line in those files. They are xml files.

[DanPristupov]

They both have long lines.

They are too large to display by default, then.

#496 (comment)

[ronnieshipman]

What is the default maximum line length? Because the lengths I gave you are the max lengths in the files. The lengths of the lines with changes on are as follows:
File with no issue: Change makes line length go from 327 to 334.
File with issue: Change makes line length go from 343 to 350.