diff options
| author | blasty <blasty@local> | 2026-07-10 16:17:50 +0200 |
|---|---|---|
| committer | blasty <blasty@local> | 2026-07-10 16:17:50 +0200 |
| commit | 33bd85e41221a82a8ee7b71d39eda59d89b78ee7 (patch) | |
| tree | 834cfe94671246b35c9592a38baa372df65ed3f4 /docs | |
| parent | app: comment on a no-address line -> function comment (was refused) (diff) | |
| download | ida-tui-33bd85e41221a82a8ee7b71d39eda59d89b78ee7.tar.gz ida-tui-33bd85e41221a82a8ee7b71d39eda59d89b78ee7.tar.xz ida-tui-33bd85e41221a82a8ee7b71d39eda59d89b78ee7.zip | |
drive: ergonomic RE helper over the RPC socket (terse text, auto socket)
Driving via rpcclient meant re-exporting the socket every fresh shell,
long invocations, and piping ~every call through python -c to pull one
field or grep pseudocode. idatui.drive fixes that: it auto-resolves the
socket (the single live pane from the registry), prints compact text
instead of JSON, and bundles the common gestures:
where | go | pc <fn> [substr] | dis <fn> [n] | callees/callers <fn> |
names <substr> | rename <old> <new> | mv old=new... | note <fn> <text> |
screen | raw <method> k=v
So 'goto+rename+parse' becomes 'drive rename old new', and 'pseudocode |
python -c grep' becomes 'drive pc fn needle'. rpcclient stays the raw
transport. rpc_smoke drives it end-to-end (29 green).
Diffstat (limited to 'docs')
0 files changed, 0 insertions, 0 deletions