Commit 657e8332 authored by Dan Nicolaescu's avatar Dan Nicolaescu
Browse files

(terminal-init-xterm): Experiment with a longer

timeout.
parent 5eceba81
2007-10-23 Dan Nicolaescu <dann@ics.uci.edu>
* term/xterm.el (terminal-init-xterm): Experiment with a longer
timeout.
2007-10-23 Katsumi Yamaoka <yamaoka@jpl.org>
* emacs-lisp/advice.el (ad-make-advised-docstring):
......
......@@ -480,9 +480,14 @@
(send-string-to-terminal "\e[>0c")
;; The reply should be of the form: \e [ > NUMBER1 ; NUMBER2 ; NUMBER3 c
(when (equal (read-event nil nil 0.1) ?\e)
(when (equal (read-event nil nil 0.1) ?\[)
(while (not (equal (setq chr (read-event nil nil 0.1)) ?c))
;; If the timeout is completely removed for read-event, this
;; might hang for terminals that pretend to be xterm, but don't
;; respond to this escape sequence. RMS' opinion was to remove
;; it completely. That might be right, but let's first try to
;; see if by using a longer timeout we get rid of most issues.
(when (equal (read-event nil nil 2) ?\e)
(when (equal (read-event nil nil 2) ?\[)
(while (not (equal (setq chr (read-event nil nil 2)) ?c))
(setq str (concat str (string chr))))
(when (string-match ">0;\\([0-9]+\\);0" str)
;; NUMBER2 is the xterm version number, look for something
......
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