From: Noam Postavsky <npostavs@gmail.com>
To: Jake <jake.waksbaum@gmail.com>
Cc: 25097@debbugs.gnu.org
Subject: bug#25097: 25.1; Scratch buffer flashes with emacsclient and xterm
Date: Wed, 09 May 2018 20:44:28 -0400 [thread overview]
Message-ID: <87vabwl4pf.fsf@gmail.com> (raw)
In-Reply-To: <CAAE4Qiuofd+hn_Y5zRDwczmp7DHoOOynwsk1d+XmHB3UDfAZKw@mail.gmail.com> (Jake's message of "Fri, 02 Dec 2016 22:12:22 +0000")
Jake <jake.waksbaum@gmail.com> writes:
> When I run
>
> emacs -Q --daemon
> emacsclient -t foo.txt
>
> to open some file foo.txt, the scratch buffer displays for 2-3 seconds
> before the buffer for the file actually opens. My TERM environment
> variable is set to "xterm-256color", and if I change it to
> "screen-256color" this problem goes away. Also if I create a file
> containing only "(setq-default xterm-query-timeout nil)" and load that
> with the -l flag, the problem goes away. Presumably there is a purpose
> to this timeout, so just doing this is probably not ideal. It was
> added in commit cc8f96e in response to bug#12345.
That commit actually changed the timeout from a hardcoded 2, and makes
the timeout configurable. So I think setting xterm-query-timeout to nil
is the right thing here. Perhaps even a nil xterm-query-timeout should
be the default?
Here's another case where that seems to help:
https://emacs.stackexchange.com/questions/16878/0950c-escape-code-is-inserted-with-typeahead-in-terminal-emacs
next prev parent reply other threads:[~2018-05-10 0:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-02 22:12 bug#25097: 25.1; Scratch buffer flashes with emacsclient and xterm Jake
2018-05-10 0:44 ` Noam Postavsky [this message]
2020-08-12 0:35 ` Stefan Kangas
2020-08-12 14:11 ` Eli Zaretskii
2020-08-12 14:18 ` Stefan Kangas
2020-08-12 14:47 ` Eli Zaretskii
2021-12-01 19:37 ` Lars Ingebrigtsen
[not found] <CG4B2Q18ULAQ.1HTM4A3C0W2ZD@tsav>
2021-12-01 22:30 ` 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=87vabwl4pf.fsf@gmail.com \
--to=npostavs@gmail.com \
--cc=25097@debbugs.gnu.org \
--cc=jake.waksbaum@gmail.com \
/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.