From: Jim Paris <jim@jtan.com>
To: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org, dickey@invisible-island.net, 5541@debbugs.gnu.org
Subject: Re: bug#5541: 23.1; after upgrading to emacs-23, meta key in xterm no longer works
Date: Sat, 13 Mar 2010 17:09:34 -0500 [thread overview]
Message-ID: <20100313220934.GA23155@psychosis.jim.sh> (raw)
In-Reply-To: <876350rmmx.fsf@stupidchicken.com>
Chong Yidong wrote:
> Glenn Morris <rgm@gnu.org> writes:
>
> >> Does anyone on this list have xterm-253 available to test?
> >
> > Yes.
> >
> >>> 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.
> >
> > Something similar happens for me too (and with the trunk).
>
> And does xterm-24* behave OK?
>
> It's possible this is a bug in xterm-253, which would be why Sven
> Joachim does not see it on xterm-255.
I did some more testing and it only happens on some of my systems.
Turns out the problem shows up when this .Xresources setting is
present:
! Shift-paste to paste CLIPBOARD instead of PRIMARY.
xterm*VT100.Translations: #override \
Shift <Btn2Up>: insert-selection(CLIPBOARD)\n \
Ctrl ~Shift Meta <Key>-: smaller-vt-font() \n \
Ctrl ~Shift Meta <Key>=: larger-vt-font() \n
That's worked for me forever... I have no idea why it would cause new
versions of emacs to act funny. CCing Thomas Dickey, any ideas?
The original report is at http://debbugs.gnu.org/cgi/bugreport.cgi?bug=5541
-jim
next prev parent reply other threads:[~2010-03-13 22:09 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
2010-03-13 19:57 ` Glenn Morris
2010-03-13 20:29 ` bug#5541: " Chong Yidong
2010-03-13 22:09 ` Jim Paris [this message]
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=20100313220934.GA23155@psychosis.jim.sh \
--to=jim@jtan.com \
--cc=5541@debbugs.gnu.org \
--cc=cyd@stupidchicken.com \
--cc=dickey@invisible-island.net \
--cc=emacs-devel@gnu.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 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).