From: Sven Joachim <svenjoac@gmx.de>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: Jim Paris <jim@jim.sh>, 5541@debbugs.gnu.org, emacs-devel@gnu.org
Subject: Re: 23.1; after upgrading to emacs-23, meta key in xterm no longer works
Date: Sat, 13 Mar 2010 20:10:41 +0100 [thread overview]
Message-ID: <87bpesxcjy.fsf@turtle.gmx.de> (raw)
In-Reply-To: <873a04ysew.fsf@stupidchicken.com> (Chong Yidong's message of "Sat, 13 Mar 2010 13:42:47 -0500")
On 2010-03-13 19:42 +0100, Chong Yidong wrote:
> Does anyone on this list have xterm-253 available to test? I can't
> reproduce the problem on xterm 241, and don't have xterm-253 available
> to test at the moment.
With xterm 255 I cannot reproduce the problem either (xterm 253 is not
available here).
Sven
>> With "emacs23 -nw" running inside xterm-253, my meta key does not work
>> for things like M-x. Instead, the terminal bell beeps, and the string
>> ;120~ appears in the buffer. Looking at the log below, this is
>> because the terminal actually sent the string \e[27;3;120~ which is
>> occurring because emacs turned on the "modifyOtherKeys" setting with
>> the escape sequence \e[>4;1m at startup. Older versions of emacs did
>> not do this, and everything worked fine.
>>
>> Indeed, if I execute the command:
>> (xterm-turn-off-modify-other-keys (selected-frame))
>> then my meta key temporarily starts working again.
>>
>> My normal Xterm settings are
>> xterm*metaSendsEscape: true
>> xterm*eightBitInput: false
>> which has always worked in previous versions.
next prev parent reply other threads:[~2010-03-13 19:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-13 18:42 23.1; after upgrading to emacs-23, meta key in xterm no longer works Chong Yidong
2010-03-13 19:10 ` Sven Joachim [this message]
2010-03-13 19:57 ` Glenn Morris
2010-03-13 20:29 ` bug#5541: " Chong Yidong
2010-03-13 22:09 ` Jim Paris
2010-03-13 23:57 ` Thomas Dickey
2010-03-14 19:05 ` Glenn Morris
2010-03-14 12:51 ` Eduard Wiebe
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bpesxcjy.fsf@turtle.gmx.de \
--to=svenjoac@gmx.de \
--cc=5541@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=emacs-devel@gnu.org \
--cc=jim@jim.sh \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).