>>>>> Daniel Shahaf <danie...@apache.org>: > No, you should be looking for the sequence of bytes starting at offset > 1916. So, the bytes are:
> 53564e0100008c0c823d > (for example, 'xxd -s 1916 -l 10 -ps' will tell you that) Um... how do one determine the length of the sequence? You are using 10 bytes I guess...? Anyway, the sequence you are showing about, starting at 1916 is the only one in the file, both when searching forward and backwards, in ghex. > And please don't try searching for the text representation on the > right hand side of the hex view! (You've been here long enough that I > assume you know that, but you said 'search for "ENDREP.DELTA.SVN"', > which is incorrect in so many ways...) Yes, I was just trying my way around hexl-mode, and it proved to have too limited search capabilities. And I was also hoping that there would be human readable strings that could be used to identify the contents. Re: 2247 >> I tried searching for "x^.Rmo.@", but the one at the cursor is the only >> occurrence in the file. At least the only aligned so that search will >> find it. Doesn't look like hexl-mode has the possibility to search for >> a byte sequence. Maybe I should get myself a proper hex editor? I installed ghex, and there I've searched for "78 5E 1D 52 6D 6F DA", and there is only one occurrence of that strng in the file.
