DHEX_SEARCHLOG(5)

💖 DHEX_SEARCHLOG 💖

okay bestie, so this is the manpage for dhex_searchlog — it's a LOCAL manual page, and it's literally just here to explain the format of searchlog files, no cap.

✨ NAME ✨

dhex_searchlog — search log file for dhex

🌸 DESCRIPTION 🌸

Searchlogs for dhex(1) are stored in searchlog files, and this manpage describes the format of those files. that's it, that's the whole job. slay.

🎀 EXAMPLE 🎀

a typical searchlog file looks exactly like this, no edits, no vibes-based tweaking:

‘#DHEX SEARCHLOG’
‘#VERSION 0’
‘#Search was for d0 0f af fe’
‘#lines are all in hex’
‘0000000000002385’
‘0000000000002e21’
‘0000000000006acb’
‘0000000000006b8b’
‘000000000000cd27’

👑 OPTIONS 👑

in the example above, the file has two sections: a comment section, and an offset section. iconic structure honestly.

💅 Comments

Comments are indicated with a '#' character. Everything afterwards in a line is being ignored when parsing the file. so like, # is the "not me, don't read this" marker. periodt.

🦋 Offset section

Offsets are 64 bit addresses presented as hexadecimal values. It is the offset where the searchstring occurred as result when the searchlog was written. And it is also where the next search is being conducted when reading the searchlog. so like, it's giving both "where it happened" and "where we're going next" — main character energy fr fr.

💀 BUGS 💀

Report bugs to <dettus@dettus.net>. Make sure to include DHEX somewhere in the subject. (yes, actually put DHEX in there, it's not optional, the maintainer is asking nicely 🙈)

🌈 AUTHOR 🌈

Written by Thomas Dettbarn

⭐ SEE ALSO ⭐

dhex(1), dhexrc(5), dhex_markers(5).

and that's the whole page bestie 💜 this one came out of the Debian source, dated May 12, 2012, and the manual name on the header was DHEX_SEARCHLOG(5) — go read the other three pages too, iykyk 🫶✨