-
-
Notifications
You must be signed in to change notification settings - Fork 238
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
(Partial) compatibility with xxd? #121
Comments
Another xxd feature that I find is most lacking is -r (reverse hexdump).
|
We now have a new |
It is basically the same as |
I see, thanks. I believe we should change it to |
For `xxd`-compatibility reasons see #121
Fixed in 1df35ee.
That is indeed pretty cool. This would be a major new feature and I don't currently plan on adding it to |
I think it would be interesting to try and maintain some level of compatibility with
xxd
. I recently came across this when following a blog post, trying to usehexyl
instead ofxxd
.--length
/--bytes
, i.e.-l
in addition to-n
and-c
.xxd
is the-groupsize
option. This is already being discussed in Other sizes of data (group size and Endianness) #104.What other flags/options could we try to support or try to provide aliases for?
What we're definitely not going to support is long single-dash options like
-groupsize
. Instead, we are always going to keep a style where long options come with two dashes--groupsize
.By the way, one thing that we already do better:
So instead of
xxd -s $((0x2118)) ./hello
we can simply sayhexyl -s 0x2118 ./hello
.Note: we already try to be (partially) compatible with
hexdump
.The text was updated successfully, but these errors were encountered: