Commit 3b0055e3 authored by Per Bothner's avatar Per Bothner

Document click-move option.

parent dfc6b256
......@@ -55,6 +55,8 @@ application; if that is unavailable, the name of the application.
> Then start a new command, and enter prompt mode: Subsequent text
> (until a `OSC "133;B"` or `OSC "133;I"`command) is a prompt string.
> Applicable options: `aid`, `click-move`.
`OSC "133;N"` _options_ `"\007"`
> Same as `OSC "133;A"` but may first implicitly terminate a previous command:
......@@ -63,6 +65,8 @@ application; if that is unavailable, the name of the application.
> (as well as any other commands nested more deeply).
> If no `aid` is specified, treat as an `aid` whose value is the empty string.
> Applicable options: `aid`, `click-move`.
`OSC "133;P"` _options_ `"\007"`
> Start of secondary prompt. This is used for multi-line prompts,
......@@ -80,7 +84,7 @@ application; if that is unavailable, the name of the application.
> End of input, and start of output.
`OSC "133;Z"`_options_ `"\007"`
`OSC "133;Z"` _options_ `"\007"`
> End of current command.
......@@ -116,11 +120,40 @@ A terminal must ignore an _option_ whose _option-name_ it doesn't recognize.
> where 0 means successful completion, and non-zero for failure.
`click-move=` _value_
> The _value_ can be `line` or other options to be determined later.
> This is a request from the application to the terminal to
> This option is defined for `A` or `N` commands.
> This option is a request from the application to the terminal to
> translate clicks in the input area to cursor movement.
> The terminal is free to ignore this option.
> The terminal is free to ignore this option, or to treat
> any specified _value_ as `line`.
> See separate discussion below.
> If implemented. it provides a more natural user experience,
> especially for beginners, who are often surprised when a mouse
> click doesn't move the cursor.
> The _value_ can be one of `line`, `multi`, `vmove`, or `vmove+`,
> specifying what kind of cursor key sequences are handled by the application.
> The value `line` allows motion within single input line, using
> using standard left/right arrow escape sequences
> (or overridden by `'move-keys`). Only a single left/right sequence
> should be emitted for double-width characters.
> The value `multi` allows movement between different lines
> (in the same group), but only using left/right arrow escape sequences.
> The values `vmove` or `vmove+` is like `multi` but cursor up/down should
> be used.
> Using `vmove+` specifies that that there are no spurious spaces
> (written by the application though not typed by the user)
> at the end of the line, _and_ that the application editor handles
> "smart vertical movement". (This means that moving 2 lines up from
> character position 20, where the intermediate line is 15 characters wide
> and the destination line is 18 characters wide, ends at position 18.)
> If `vmode` is specified instead of `vmode+` then the terminal
> should be more conservative when moving between lines:
> It should move the cursor left to the start of line, then emit the needed
> up or down sequences, then move the cursor right to the clicked destination.
> To support extensions, _value_ is allowed to be a comma-separated list.
`move-keys=` _left_ `","` _right_ [`","` _up_, `","` _down_]
> Specify key sequences to use for `click-move` mode when
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment