aboutsummaryrefslogtreecommitdiffstats
path: root/tools/verify_procs.py
diff options
context:
space:
mode:
authorblasty <blasty@local>2026-08-06 16:36:53 +0200
committerblasty <blasty@local>2026-08-06 16:36:53 +0200
commit1eed36ec1cdd573ef5a095dcafff12a6dd4daab2 (patch)
tree2d21dbc913f5a8398ff5ecf237be9b7c8e001aa3 /tools/verify_procs.py
parentgraph: navigate to blocks, not to coordinates (diff)
downloadida-tui-1eed36ec1cdd573ef5a095dcafff12a6dd4daab2.tar.gz
ida-tui-1eed36ec1cdd573ef5a095dcafff12a6dd4daab2.tar.xz
ida-tui-1eed36ec1cdd573ef5a095dcafff12a6dd4daab2.zip
help: reach the cheatsheet with H as well as F1
F1 is swallowed before it ever reaches us on at least one setup here -- the app's own binding fires when the key is injected directly, zellij has no F1 binding of its own, and every common F1 encoding written straight into the pane (SS3 ESC O P, CSI ESC [11~, CSI-u ESC [1;1P) opens it. So the key is being eaten by something upstream, which is not ours to fix, and a cheatsheet reachable only through a function key is fragile anyway: terminals and multiplexers claim them routinely. H opens and closes it too. '?' stays with the incremental search, which is what it has always done in the code views.
Diffstat (limited to 'tools/verify_procs.py')
0 files changed, 0 insertions, 0 deletions