aboutsummaryrefslogtreecommitdiffstats
path: root/docs/TUI_DRIVING_BLUEPRINT.md
diff options
context:
space:
mode:
authorblasty <peter@haxx.in>2026-08-06 15:11:54 +0200
committerblasty <peter@haxx.in>2026-08-06 15:11:54 +0200
commit0d4049f695dc37bf34ab8b67e936f73a2f7a3438 (patch)
tree1aa2c148419ecd8a1dcdc7eea23a9ebac30f5c32 /docs/TUI_DRIVING_BLUEPRINT.md
parentdomain: operand extents, and the formats behind them (diff)
downloadida-tui-0d4049f695dc37bf34ab8b67e936f73a2f7a3438.tar.gz
ida-tui-0d4049f695dc37bf34ab8b67e936f73a2f7a3438.tar.xz
ida-tui-0d4049f695dc37bf34ab8b67e936f73a2f7a3438.zip
app: 'o' cycles the literal under the cursor
IDA's own key, and that muscle memory is worth more than the opcode column's old claim on it -- the bytes column moves to B. The literal the cursor is on is MARKED, and that mark is what changes, because a line usually holds more than one. The cursor follows its literal across the edit: 48 <-> 0x30 reflows the line, and holding the column would put the next press on a neighbour. Land on a register -- something with no format of its own -- and it says so and names the operand that has one, rather than quietly reformatting a different one. Works in the pseudocode too, on Hex-Rays' separate number formats.
Diffstat (limited to 'docs/TUI_DRIVING_BLUEPRINT.md')
0 files changed, 0 insertions, 0 deletions