Return to BSD News archive
Xref: sserve comp.emacs.xemacs:2106 comp.unix.bsd.freebsd.misc:2578
Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!simtel!news.kei.com!news.mathworks.com!solaris.cc.vt.edu!usenet
From: mmead@Glock.COM (matthew c. mead)
Newsgroups: comp.emacs.xemacs,comp.unix.bsd.freebsd.misc
Subject: Re: XEmacs 19.12 Meta character problem from XTerm?
Date: 26 Jun 1995 04:31:28 GMT
Organization: Glock Telecommunications
Lines: 24
Message-ID: <MMEAD.95Jun26003128@Glock.COM>
References: <MMEAD.95Jun25162757@glock.com> <wingDArB36.8oI@netcom.com>
NNTP-Posting-Host: glock.com
NNTP-Posting-User: mmead
In-reply-to: wing@netcom.com's message of Mon, 26 Jun 1995 01:35:29 GMT
In article <wingDArB36.8oI@netcom.com> wing@netcom.com (Ben Wing) writes:
> In article <MMEAD.95Jun25162757@glock.com>,
> matthew c. mead <mmead@Glock.COM> wrote:
[ waaah meta-x don't work ]
> You need to make sure that your keyboard maps Alt to Meta, and you
Played with xmodmap for a long time, and am positive it does. :-)
> might have to use the resource
> XTerm*eightBitInput: false
Should it be set to true for the meta to be used as the top bit, or
false? I got it to work with (set-input-mode nil nil t).
-matt
--
Matthew C. Mead | Network Administration: Virginia Tech Center for
| Transportation Research -> mmead@ctr.vt.edu
mmead@Glock.COM | Network Administration and Software Development
http://www.Glock.COM/~mmead/ | Consulting: BizNet Technologies -> mmead@bnt.com