From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 44908@debbugs.gnu.org, jidanni@jidanni.org
Subject: bug#44908: emacs -nw: view-lossage polluted by termcap / terminfo jazz
Date: Sun, 29 Nov 2020 18:36:49 +0200 [thread overview]
Message-ID: <83pn3wktlq.fsf@gnu.org> (raw)
In-Reply-To: <874kl8f81r.fsf@gnus.org> (message from Lars Ingebrigtsen on Sun, 29 Nov 2020 17:21:20 +0100)
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: 44908@debbugs.gnu.org, jidanni@jidanni.org
> Date: Sun, 29 Nov 2020 17:21:20 +0100
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I get a *Help* buffer that has:
> >>
> >> ESC [ > ESC [ > 6 5 ; 6 2 0 1 ; 1 c ;;
> >
> > What do you have in recent-keys in that case?
>
> emacs -Q -nw --eval '(message "%s" (recent-keys))'
>
> gives me the following *Messages*:
>
> [27 91 62 27 91 62 54 53 59 54 50 48 49 59 49 99]
Does the below fix the problem? (But maybe we should still arrange
for recording these events in the dribble file? or is it impossible to
have dribble active at this point?)
diff --git a/lisp/term/xterm.el b/lisp/term/xterm.el
index 1a727e3..7094100 100644
--- a/lisp/term/xterm.el
+++ b/lisp/term/xterm.el
@@ -767,7 +767,8 @@ xterm--read-event-for-query
By not redisplaying right away for xterm queries, we can avoid
unsightly flashing during initialization. Give up and redisplay
anyway if we've been waiting a little while."
- (let ((start-time (current-time)))
+ (let ((start-time (current-time))
+ (inhibit--record-char t))
(or (let ((inhibit-redisplay t))
(read-event nil nil xterm-query-redisplay-timeout))
(read-event nil nil
next prev parent reply other threads:[~2020-11-29 16:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-27 19:25 bug#44908: emacs -nw: view-lossage polluted by termcap / terminfo jazz 積丹尼 Dan Jacobson
2020-11-29 10:23 ` Lars Ingebrigtsen
2020-11-29 15:47 ` Eli Zaretskii
2020-11-29 16:21 ` Lars Ingebrigtsen
2020-11-29 16:36 ` Eli Zaretskii [this message]
2020-11-30 10:19 ` Lars Ingebrigtsen
2020-11-30 18:48 ` Eli Zaretskii
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83pn3wktlq.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=44908@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=larsi@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.