Awesome. In my book you're a super hero ;) Thanks for the quick mod.
On Tue, Apr 21, 2009 at 5:36 AM, pancake <[email protected]> wrote: > Thanks for the proposal. Nibble will kill me :P he told me that we should > do something like this and > I disagreed, but now with this pretty example i can say that maybe an > useful option. Pull hg tip, > there's a commit adding a new 'scr.bytewidth' eval variable to configure > the byte width output for > px, po, pb > > Originally all print modes are affected by the scr.width variable which > defines the width of the screen > and then radare automatically fits the contents of the dump to the desired > value (or the terminal one > if not defined). But allowing to choose the bytewidth is probably a more > precise way to do it. > > Now scr.width and scr.bytewidth affects to the output of some 'p'rint > formats. > > Thanks for the tip > > --pancake > > Demonic Software wrote: > >> I am staring at some data dumps of a disk, and I would like to adjust the >> hexadecimal output. Right now the block size is set at 512, but the width >> of the 512 block is 38 bytes. I would like to adjust the width so that it >> is 8/16/32 bytes so I can quickly look at the fields. I am not sure if this >> is possible, but the current output looks something like this. I am not >> superhuman, so reading and comparing >> >> >> offset 0 1 2 3 4 5 6 7 8 9 A B C D E F >> 0 1 2 3 4 5 6 7 8 9 A B C D E F 0 1 2 3 4 5 >> 0x00000000, 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0x00000026 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 0000 0000 0000 >> 0x0000004c, 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 0000 0000 0000 >> 0x00000072 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 0000 0000 0000 >> 0x00000098, 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 0000 0000 0000 >> >> I want to adust it so it looks like this: >> >> offset 0 1 2 3 4 5 6 7 8 9 A B C D E F >> 0x00000000, 0000 0000 0000 0000 0000 0000 0000 0000 >> 0x00000010, 0000 0000 0000 0000 0000 0000 0000 0000 >> 0x00000020, 0000 0000 0000 0000 0000 0000 0000 0000 >> ... >> 0x00000400, 0000 0000 0000 0000 0000 0000 0000 0000 >> >> or adjust it to: >> >> offset 0 1 2 3 4 5 6 7 8 9 A B C D E F >> 0 1 2 3 4 5 6 7 8 9 A B C D E F 0x00000000, >> 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 >> 0x00000020 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 >> 0x00000040, 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 >> ... >> 0x00000400, 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 0000 >> 0000 0000 0000 0000 >> >> >> I did not see anything in the documentation, which makes me wonder if its >> possible. Thanks for the help in advance. >> >> >> dsoftware >> ------------------------------------------------------------------------ >> >> _______________________________________________ >> radare mailing list >> [email protected] >> http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org >> >> > _______________________________________________ > radare mailing list > [email protected] > http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org >
_______________________________________________ radare mailing list [email protected] http://lists.nopcode.org/listinfo.cgi/radare-nopcode.org
