aboutsummaryrefslogtreecommitdiffstats
path: root/experiments/bench_pack_trace.py
diff options
context:
space:
mode:
authorblasty <blasty@local>2026-08-09 23:01:22 +0200
committerblasty <blasty@local>2026-08-09 23:01:22 +0200
commitcdeec8ba1fab499e64dfbbd2599afddb8a9d9dea (patch)
treeb45bc548bf96a1fed434a6941d2f020b8c7c2022 /experiments/bench_pack_trace.py
parentShip the idatui agent skill in-repo at .agents/skills/ (diff)
downloadida-tui-cdeec8ba1fab499e64dfbbd2599afddb8a9d9dea.tar.gz
ida-tui-cdeec8ba1fab499e64dfbbd2599afddb8a9d9dea.tar.xz
ida-tui-cdeec8ba1fab499e64dfbbd2599afddb8a9d9dea.zip
README: cut the wall of text out of 'What's in it'
The feature coverage was right, the prose was not: eleven paragraphs that explained MECHANISM in an intro document. The keys table right above it already proved that scannable beats thorough here. Every feature is now name + key + at most two lines. Longest block went from ~70 words to 35; the section from 80 lines to 53. What got cut was rationale, not information, and none of it is lost -- each one is already the docstring of the module that implements it: why findings has to journal edits (journal.py), how search guesses text vs bytes (search.py), trail painting and unseen bytes as ?? (trace.py), why terminal graphics support is asked for rather than sniffed (kittygfx.py). The README now says what a feature IS and links onward. Also folded hex/strings/palettes/projects/splash into one 'Also' line (all already in the keys table), and gave the same treatment to the Run prose and the agent-skill paragraph.
Diffstat (limited to 'experiments/bench_pack_trace.py')
0 files changed, 0 insertions, 0 deletions