From 865d3142340684acdbbe4cde9890ee7ea7e59982 Mon Sep 17 00:00:00 2001 From: worldmozara Date: Mon, 26 Oct 2026 00:53:08 +0800 Subject: [PATCH] docs: say the terminal keeps its own prompt line A prompt answered from the notification reads both surfaces; the terminal still shows the keys it takes, which a button cannot say. --- doc/notifications.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/doc/notifications.md b/doc/notifications.md index 3caeea9..98e66f9 100644 --- a/doc/notifications.md +++ b/doc/notifications.md @@ -84,7 +84,9 @@ back through a surface that outlives it. A prompt that can be answered from the notification reads both surfaces while it blocks, from the first moment — the notification itself only shows up after `grace_seconds`, so waiting for it to appear before listening would block on the -terminal alone. Typing at the terminal always wins; a readline-only convenience +terminal alone. The terminal keeps its own prompt line with the keys it accepts — +a button elsewhere does not say what typing here would do. Typing at the terminal +always wins; a readline-only convenience (Tab completion on `ask_user_line`) is what a question gives up in exchange. A prompt that *follows* an answer given on the notification — the "why denied"