diff --git a/doc/pages/commands.asciidoc b/doc/pages/commands.asciidoc index e182696e..b2089273 100644 --- a/doc/pages/commands.asciidoc +++ b/doc/pages/commands.asciidoc @@ -284,11 +284,20 @@ but not really useful in that context. prompt content will be passed as a single token. In other words, word splitting does not take place. + NOTE: The prompt is displayed in and receives input from the + current client context, so inside a draft context like + `evaluate-commands -draft`, it is invisible and only responds to + an `execute-keys` command in the same context. + *on-key* :: wait for next key from user, then execute , the key is available through the `key` value, accessible through `$kak_key` in shells, or `%val{key}` in commands. + NOTE: The key press must come from the current client context, + so inside a draft context like `evaluate-commands -draft`, it only + responds to an `execute-keys` command in the same context. + *menu* [] ...:: display a menu using labels, the selected label’s commands are executed. The *menu* command can take an *-auto-single* argument, to automatically @@ -297,6 +306,11 @@ but not really useful in that context. last one being a command to execute when the item is selected (but not validated) + NOTE: The menu is displayed in and receives input from the + current client context, so inside a draft context like + `evaluate-commands -draft`, it is invisible and only responds to + an `execute-keys` command in the same context. + *info* [] :: display text in an information box with the following *switches*: @@ -329,6 +343,9 @@ but not really useful in that context. parse markup in both title (if provided) and text. (See <>) + NOTE: The info box is displayed in the current client context, + so inside a draft context like `eval -draft`, it is invisible. + *try* [catch ]...:: prevent an error in *commands* from aborting the whole command execution, execute *on_error_commands* instead. If nothing is to be