From: Eli Zaretskii <eliz@gnu.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: 23819@debbugs.gnu.org
Subject: bug#23819: 25.0.95; display botched badly in xterm window
Date: Wed, 22 Jun 2016 22:00:23 +0300 [thread overview]
Message-ID: <838txx3v7c.fsf@gnu.org> (raw)
In-Reply-To: <576ADF3D.2050908@cs.ucla.edu> (message from Paul Eggert on Wed, 22 Jun 2016 20:55:57 +0200)
> Cc: 23819@debbugs.gnu.org
> From: Paul Eggert <eggert@cs.ucla.edu>
> Date: Wed, 22 Jun 2016 20:55:57 +0200
>
> > The "ESC [ > 1;3201;0c" thingy is the response to query by
> > xterm--query, see xterm--version-handler. Is it true that all these
> > problems happen right in the beginning of a session? What happens if
> > you wait at least 2 sec after starting a session, without typing any
> > commands -- do these problems still happen?
>
> I have observed the problem in later parts of a session. In particular,
> after a problem occurs and I type control-L to refresh the screen
> completely, I have observed the problem recur in the same Emacs session.
> Typically the problem occurs during interactive search, when substrings
> are being highlighted in the text and in the minibuffer. Typically I am
> searching code, where keywords and suchlike are also highlighted. I
> assume all this highlighting is being done in the background.
When you say "the problem" here, do you mean the "ESC [ > ..."
response? IOW, do you see this sequence in Emacs input stream in the
middle of a session? That would be highly unusual, as AFAIK we only
query the terminal at the session beginning.
next prev parent reply other threads:[~2016-06-22 19:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-22 2:01 bug#23819: 25.0.95; display botched badly in xterm window Paul Eggert
2016-06-22 14:54 ` Eli Zaretskii
2016-06-22 18:55 ` Paul Eggert
2016-06-22 19:00 ` Eli Zaretskii [this message]
2016-06-22 21:27 ` Paul Eggert
2016-06-22 19:04 ` Eli Zaretskii
2016-06-23 8:58 ` Paul Eggert
2016-06-23 14:53 ` Eli Zaretskii
2022-01-29 16:55 ` Lars Ingebrigtsen
2022-01-30 2:53 ` Paul Eggert
2022-01-30 16:01 ` Lars Ingebrigtsen
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=838txx3v7c.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=23819@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
/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.