From 7ae37ba3b432bbb2482df9c99864350e685b0241 Mon Sep 17 00:00:00 2001 From: blasty Date: Fri, 10 Jul 2026 16:43:32 +0200 Subject: app: multi-line comments via literal \\n (long notes were clipping) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The comment prompt is single-line, so a long note rendered as one giant '//' line that ran off the right edge and got clipped. Interpret a literal '\\n' (backslash-n) in the comment text as a real newline in _do_comment (the single choke point for the ';' prompt and the RPC 'comment' verb) — Hex-Rays renders each as its own '//' line. Verified live and locked in the comment_func scenario (multi-line render); suite 104 green. --- docs/RPC.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'docs') diff --git a/docs/RPC.md b/docs/RPC.md index 5cb73ee..4a68fbe 100644 --- a/docs/RPC.md +++ b/docs/RPC.md @@ -81,7 +81,7 @@ predicate so the returned state is final. |--------|--------|--------| | `goto` / `open` | `target`, `delay_ms?`, `timeout?` | `g` prompt → name or `0xADDR` → Enter. | | `rename` | `name`, `word?`, `delay_ms?` | `n` on the token under the cursor → replace → Enter. `word` first places the cursor on that token (see `cursor_on`). | -| `comment` | `text`, `delay_ms?` | `;` on the current line. | +| `comment` | `text`, `delay_ms?` | `;` on the current line (a literal `\n` in `text` becomes a real newline → multi-line comment). | | `retype` | `proto`, `word?`, `delay_ms?` | `y` on the token/function under the cursor (`word` places it first). | | `follow` | `word?` | Enter: follow the reference under the cursor (`word` places it first); waits for the jump. | | `back` | — | Escape: pop the nav stack. | -- cgit v1.3.1-sl0p