Xref: utzoo gnu.bash.bug:2402 comp.windows.x:36522 Path: utzoo!utgpu!news-server.csri.toronto.edu!rutgers!stanford.edu!snorkelwacker.mit.edu!ai-lab!ai.mit.edu!gnulists From: mike-w@cs.aukuni.ac.nz Newsgroups: gnu.bash.bug,comp.windows.x Subject: Re: Why is bash-1.07 setup by default for 7 bit ? Message-ID: Date: 17 May 91 13:35:52 GMT References: <9105111648.AA02969@life.ai.mit.edu> Followup-To: gnu.bash.bug Organization: is for wimps Lines: 31 Approved: info-gnu@prep.ai.mit.edu In-Reply-To: mike-w@cs.aukuni.ac.nz's message of 13 May 91 21:19:27 GMT Nntp-Posting-Host: cs17.cs.aukuni.ac.nz X-News-Software: GNUS 3.13 Apparently-To: gnu-bash-bug@uunet.uu.net >>> On 13 May 91 21:19:27 GMT, in gnu.bash.bug >>> "Me" == mike-w@cs.aukuni.ac.nz writes: Me> I'm running 1.07-cwru, but still can't get the Meta key working in an Me> xterm window. I've tried 'stty pass8', and several other stabs in the Me> dark ... any better ideas ?? Thanks to all those who replied. Since there was such a variety of responses, I thought I'd summarise: I was rather hasty in posting this to gnu.bash.bug ... the problem was with xterm itself (having recently moved to a R4 xterm). * In the R4 xterm translation table, the event "Meta" is bound to `insert-eight-bit'. However, "Meta" in this context means "Meta_L or Meta_R" rather than "a mod1 modifier". * The "Meta" key on my keyboard actually sends the "Alt_L" keysym by default, so although it was registered as a "mod1" modifier, and treated as Meta by other Xclients (eg. emacs, R3 xterm) R4 xterm did not grok it as a Meta key. * The solution (with thanks to Liam Breck ) was xmodmap -e "keysym Alt_L = Meta_L" -- /-------------------- mike-w@cs.aukuni.ac.nz ---------------------\ | Mike Williams, Computer Science, Auckland University, Aotearoa. | \-------------- What's another word for Thesaurus? ---------------/ -- New administrater uofa.