Xref: utzoo gnu.emacs.help:594 comp.windows.x:30679 Path: utzoo!utgpu!cunews!bnrgate!uunet!shelby!mcnc!rti!dg-rtp!dg-rtp!brennan From: brennan@rtp.dg.com (Dave Brennan) Newsgroups: gnu.emacs.help,comp.windows.x Subject: Emacs under X (use of XLookupString) Message-ID: Date: 14 Dec 90 22:08:30 GMT Sender: usenet@dg-rtp.dg.com (Usenet Administration) Organization: Data General, RTP, NC Lines: 37 This occurs using Emacs 18.55, Epoch 3.2, and X11R4 under DG/UX. Is anyone aware of anything Emacs (and/or Epoch) does which would affect the results of XLookupString? The problem I'm seeing is that in other X applications (like xev) is the XLookupString is returning different information for the exact same keypresses under two different applications. This happens when a modifer key is used on an Sweedish keyboard to generate ASCII characters. I suspect there may be some strange processing going in our server or libraries with respect to the modifer key, but that still doesn't explain why two different applications linked with the same libX11.a behave differently, unless Emacs or Epoch is doing something else funny. By default the modifer keysym (Alt_R) is on mod bit 1, but if I move it to mod bit 3 both applications behave correctly. It seems like XLookupString should care about the modifer bit set, not the specific keysym. Since it doesn't seem to matter what modifer bit the Alt_R keysym sets, it appears that this isn't the case. Here's one entry from "xmodmap -pk" for a key that generates the vertical bar when the Alt_R key is down. I was unable to find any useful documentation on exactly what the third column entry means (or the forth if there was one). There are 4 KeySyms per KeyCode; KeyCodes range from 8 to 133. KeyCode Keysym (Keysym) ... Value Value (Name) ... 20 0x003c (less) 0x003e (greater) 0x007c (bar) |\ Dave Brennan | \____oo_ brennan@rtp.dg.com =========================================((__| /___> ...rti!dg-rtp!brennan User Interfaces, Data General | // daveb@rpitsmts.bitnet Research Triangle Park, NC |// Phone: (919) 248-6330