Doc fix for xterm-extra-capabilities

* lisp/term/xterm.el (xterm-extra-capabilities): Doc fix.

* etc/PROBLEMS: Mention xterm-extra-capabilities issue.

1 files changed, 17 insertions, 0 deletions

diff --git a/etc/PROBLEMS b/etc/PROBLEMS
index ae3f49868b2..939ce9f246d 100644
--- a/etc/PROBLEMS
+++ b/etc/PROBLEMS
@@ -1679,6 +1679,23 @@ recommended way of turning on Font-lock is by typing "M-x
 global-font-lock-mode RET" or by customizing the variable
 `global-font-lock-mode'.
 
+** Unexpected characters inserted into the buffer when you start Emacs.
+See eg http://debbugs.gnu.org/11129
+
+This can happen when you start Emacs in -nw mode in an Xterm.
+For example, in the *scratch* buffer, you might see something like:
+
+  0;276;0c
+
+This is more likely to happen if you are using Emacs over a slow
+connection, and begin typing before Emacs is ready to respond.
+
+This occurs when Emacs tries to query the terminal to see what
+capabilities it supports, and gets confused by the answer.
+To avoid it, set xterm-extra-capabilities to a value other than
+`check' (the default).  See that variable's documentation (in
+term/xterm.el) for more details.
+
 * Runtime problems specific to individual Unix variants
 
 ** GNU/Linux