Comments on Why does a reverse hexdump truncate the message?
Parent
Why does a reverse hexdump truncate the message?
$ echo "4c 6f 72 65 6d 20 69 70 73 75 6d 20 64 6f 6c 6f 72 20 73 69 74 20 61 6d 65 74 2c 20 63 6f 6e 73 65 63 74 65 74 75 72 20 61 64 69 70 69 73 63 69 6e 67 20 65 6c 69 74 2c" | xxd -r
orem ipsum dolor
The actual message here is much longer, but the first letter and most of the rest are not shown. Why not?
Post
The following users marked this post as Works for me:
| User | Comment | Date |
|---|---|---|
| TRiG |
Thread: Works for me Thanks. I'd missed that. Oddly, combining the flags as |
Jul 25, 2023 at 12:34 |
From man xxd, the section on the -r flag (emphasis added):
-r | -revert
reverse operation: convert (or patch) hexdump into binary. If not writing to stdout, xxd writes into its output file without truncating it. Use the combination -r -p to read plain hexadecimal dumps without line number information and without a particular column layout. Additional Whitespace and line-breaks are allowed anywhere.
0 comment threads