summaryrefslogtreecommitdiffstats
path: root/runtime
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2020-12-29 20:53:33 +0100
committerBram Moolenaar <Bram@vim.org>2020-12-29 20:53:33 +0100
commit4d8c96d4668ac965d4e84b9676fba6d7efe62a32 (patch)
treeacaaada4eddf51350a21b7d2263121fae2a29c92 /runtime
parent285b15fce164ade8b1537b884cc15aebaa60e9ef (diff)
patch 8.2.2246: cursor keys not recognized at the hit-Enter promptv8.2.2246
Problem: Cursor keys not recognized at the hit-Enter prompt after executing an external command. Solution: Change the codes for the extra cursor keys. (closes #7562) Tune the delays to avoid test flakyness.
Diffstat (limited to 'runtime')
-rw-r--r--runtime/doc/term.txt4
1 files changed, 4 insertions, 0 deletions
diff --git a/runtime/doc/term.txt b/runtime/doc/term.txt
index 87e56240fb..0093a96799 100644
--- a/runtime/doc/term.txt
+++ b/runtime/doc/term.txt
@@ -217,6 +217,10 @@ it's different from Alt). They can be combined. Examples: >
Another speciality about these codes is that they are not overwritten by
another code. That is to avoid that the codes obtained from xterm directly
|t_RV| overwrite them.
+
+Another special value is a termcap entry ending in "@;*X". This is for cursor
+keys, which either use "CSI X" or "CSI 1 ; modifier X". Thus the "@"
+stands for either "1" if a modifier follows, or nothing.
*xterm-scroll-region*
The default termcap entry for xterm on Sun and other platforms does not
contain the entry for scroll regions. Add ":cs=\E[%i%d;%dr:" to the xterm