ida-tui.git, branch maintui for headless idahttps://git.sl0p.foo/ida-tui.git/atom/?h=main2026-08-21T10:24:17ZTODO: change notifications and discard-changes landed with PR #12026-08-21T10:24:17Zblastypeter@haxx.in2026-08-21T10:24:17Zurn:sha1:73955f4efd6648a794aecd7ba413dc283a814bafscenarios: cover the event->UI auto-refresh path2026-08-21T10:20:02Zblastypeter@haxx.in2026-08-21T10:20:02Zurn:sha1:820c356204cb5552a2b4b4ad3591a134d1b6d1b0
PR #1's live refresh had client-level coverage only (the listener thread
and debounce, in test_nexus_client); the app half -- _refresh_idb_events
invalidating, reindexing, and reloading the active surface -- was untested.
The scenario renames straight through the client so no UI cache hears
about it (what another client's edit looks like from this process), hands
the app a synthetic batch, and requires: the status says why the view is
about to move, the listing rebuilds around the same cursor and viewport
address, the function index carries the external name, pseudocode
decompiled afterwards shows it, and a second batch landing while decomp is
active reloads it in place. That second batch also reverts the rename, so
the scenario is idempotent.
blame: ignore the ruff reformat commit2026-08-21T10:15:24Zblastypeter@haxx.in2026-08-21T10:15:24Zurn:sha1:35031392c08af950e564f8ff8c222fba8dea7cbbreformat: ruff format + import sort, mechanically (see ruff.toml)2026-08-21T10:15:15Zblastypeter@haxx.in2026-08-21T10:14:46Zurn:sha1:02d02417800184fb76cd0245cdaa94c437aa4081
No behavior. Listed in .git-blame-ignore-revs (next commit).
adopt ruff: pinned formatter + import sorting, opt-in pre-commit hook2026-08-21T10:14:27Zblastypeter@haxx.in2026-08-21T10:14:27Zurn:sha1:93ca90558aa6016e77625c627a70640e693e3303
PR #1 arrived black-formatted, which forced the question. ruff's formatter
is black's output, it is one static binary rather than a dependency chain,
and it is fast enough that a hook is free. ruff.toml pins the version
(a formatter whose output moves between releases turns 'formatted' into
'formatted by whoever committed last') and selects only import sorting on
the lint side -- a hook that refused a commit over an unused variable would
be a different feature.
.githooks/pre-commit (install: git config core.hooksPath .githooks) formats
exactly what is staged, refuses partly-staged files rather than quietly
widening a commit built with git add -p, and prefers the pinned .venv ruff.
Also drops the blanket '# ruff: noqa' PR #1 left in remote_ops.py -- it
would have exempted that file from the only lint rule we enforce.
tests: repair the two seams the ida-nexus port left behind2026-08-21T10:12:53Zblastypeter@haxx.in2026-08-21T10:12:53Zurn:sha1:ea22067c52ec335ea4d3a616cb2107d5fdbdf7b6
Two scenario monkeypatch sites still hooked client.invoke -- the rename to
call() updated the call sites but not the patches, so reprime_is_free and
split_view crashed instead of counting. call() takes the remote_ops
declaration itself now, so both count by its __name__.
remote_ops imported RemoteModule inside _bindings(), which made
test_nexus_client (NEEDS_IDA = False) unrunnable under a stdlib-only
python3 -- the house rule tests/run.py --fast depends on. The import moves
to the same eagerly-if-present, bound-to-None-so-patchable contract
nexus_client uses, and the test injects FakeRemoteModule/FakeRemoteError
exactly like its other fakes: real names when the library is installed,
strict fakes when it is not.
Merge PR #1 from mrexodia: Windows support and auto-refresh on events2026-08-21T10:09:21Zblastypeter@haxx.in2026-08-21T10:09:12Zurn:sha1:9541043c9dee7973c140159b3af561c6d0405e9e
https://github.com/blasty/ida-tui/pull/1 — from the ida-nexus (né
ida-codemode) maintainer: kitty-graphics fallback for platforms without
termios, Ctrl+R view refresh, typed remote operations through ida_nexus
RemoteModule, live auto-refresh from other clients' IDB events (upstream
item 7), discard-without-save (item 6), and the ida-nexus 0.7.0 rename.
tests/test_kittygfx.py is the union of both sides' files: our escape-
construction checks plus the PR's cross-platform fallback checks.
splash: give the logo a placement id so re-anchoring replaces, not stacks2026-08-21T10:08:42Zblastypeter@haxx.in2026-08-21T10:08:42Zurn:sha1:7a3b198a904da186cc2860df059b063db24282ea
A kitty placement is identified by (image id, placement id); an a=p with no
p= key is anonymous and every one stacks another copy. The splash re-anchors
on every progress note (~5/s), so a 60s load ended with ~300 placements of an
RGBA logo alpha-compositing over each other -- soft edges creeping to solid,
and the terminal re-rendering all of them per frame.
Same pair every time (LOGO_PLACEMENT) = the terminal REPLACES the placement,
so re-anchoring is free and atomic. That is also why on_resize no longer
clear()s first (that showed a hole for a frame), and why a shrunk-to-nothing
region now drops the placement instead of leaving a stale one anchored.
tests/test_kittygfx.py pins the escapes (pure, stdlib);
experiments/splash_place_count.py counts what a real splash sends.
Switch to ida-nexus2026-08-20T21:55:52ZDuncan Ogilviemr.exodia.tpodt@gmail.com2026-08-20T21:55:52Zurn:sha1:f4c1d9b5497fd0d38137b6b345e8171b307c1117Adopt idb_events and remote module features from ida-codemode2026-08-20T21:42:42ZDuncan Ogilviemr.exodia.tpodt@gmail.com2026-08-20T21:42:42Zurn:sha1:f3715d8de0d255c8b14710acfa120ccb9ea953fd