You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
--no-squeezing Displays all input data. Otherwise any number of groups of output lines which would be identical to the preceding group of lines, are replaced with a line comprised of a single asterisk.
It seems that lines are squeezed when they all are filled with the same single byte (for example, all 0x00 or all 0xFF). However, lines which are not filled with a single repeated byte can still be identical to previous lines. In these cases they do not appear to be squeezed.
I'll attach an example file, which contains rows filled with the two-byte word 0x1400 starting at position 00000020. If the standard two panels are displayed, I would expect this file to have data squeezed until position 00000fa0.
Thank you for reporting this. The documentation is just wrong. I don't think the squeezing feature was ever planned to work that way. But I now realize that hexdumps squeezing feature might actually do just that?
If hexdump will squeeze on identical lines always, then the squeezing feature should be changed to match hexdump. It's not difficult to make this change, I'll look at this sometime soon.
The help indicates:
It seems that lines are squeezed when they all are filled with the same single byte (for example, all 0x00 or all 0xFF). However, lines which are not filled with a single repeated byte can still be identical to previous lines. In these cases they do not appear to be squeezed.
I'll attach an example file, which contains rows filled with the two-byte word 0x1400 starting at position 00000020. If the standard two panels are displayed, I would expect this file to have data squeezed until position 00000fa0.
example.tar.gz
The text was updated successfully, but these errors were encountered: