home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.windows.x
- Path: sparky!uunet!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!news.u.washington.edu!ns1.nodak.edu!isc.cs.ndsu.nodak.edu!grosen
- From: grosen@isc.cs.ndsu.nodak.edu (Johannes Grosen)
- Subject: SUMMARY: which key(s) are Meta?
- Sender: usenet@ns1.nodak.edu (News login)
- Message-ID: <C0Furs.III@ns1.nodak.edu>
- Date: Wed, 6 Jan 1993 15:23:52 GMT
- Distribution: usa
- Nntp-Posting-Host: isc.cs.ndsu.nodak.edu
- Organization: Intelligent Systems Cluster
- Lines: 83
-
- I recently posted a question regarding how to determine which key(s)
- were my 'Meta' keys for a given X setup. I got three responses which
- are summarized below:
-
- Thanks!
-
- > From matt@centerline.com Tue Jan 5 18:11:32 1993
- >
- > There's no such thing as a "meta" key in X11 -- i.e., the X11 protocol
- > does not define any modifier named "Meta". Most applications choose
- > to use the "Mod1" modifier for their "meta"-functions. Using xmodmap
- > should tell you which key(s) apply the Mod1 modifier.
- >
- > From cana!inference.com!jaf Wed Jan 6 02:01:51 1993
- >
- > When I run xmodmap on my machine (SPARCstation 1+, SunOS 4.1.2, X11R5
- > PL18), I get:
- >
- > cana[166]% xmodmap -pm
- > xmodmap: up to 3 keys per modifier, (keycodes in parentheses):
- >
- > shift Shift_L (0x6a), Shift_R (0x75)
- > lock Caps_Lock (0x7e)
- > control Control_L (0x53)
- > mod1 Meta_L (0x7f), Meta_R (0x81)
- > mod2 Num_Lock (0x69)
- > mod3 F13 (0x20), F18 (0x50), F20 (0x68)
- > mod4
- > mod5
- >
- > I believe "mod1" is considered the META modifier by the X11R5
- > applications I run.
- >
- > If you happen to have access to a copy, in "X Window System User's
- > Guide," Chapter 12 is titled "Setup Clients" and has a whole section on
- > setting up the keyboard.
- >
- > I hope this helps. Good luck.
- >
- > From se33!jct@se01.wg2.waii.com Wed Jan 6 06:56:17 1993
- >
- > Run xmodmap with the -pm option:
- >
- > [1]--> xmodmap -pm
- > xmodmap: up to 3 keys per modifier, (keycodes in parentheses):
- >
- > shift Shift_L (0x6a), Shift_R (0x75)
- > lock Caps_Lock (0x7e)
- > control Control_L (0x53)
- > mod1 Meta_L (0x7f), Meta_R (0x81)
- > mod2 Num_Lock (0x69)
- > mod3 F13 (0x20), F18 (0x50), F20 (0x68)
- > mod4
- > mod5
- >
- > The line tagged "mod1" is your meta key. The right half of that line
- > lists the keysyms (the names) of the meta key(s); to find out which key
- > on your keyboard corresponds to that keysym name, run xev, place your
- > pointer in its window, and tap keys on the keyboard until you find the
- > key whose keysym matches those listed by xmodmap. The keysym is listed
- > in the KeyPress and KeyRelease events for each key:
- >
- > KeyRelease event, serial 15, synthetic NO, window 0x2800001,
- > root 0x2a, subw 0x0, time 473301046, (94,148), root:(993,233),
- > state 0x8, keycode 129 (keysym 0xffe8, Meta_R), same_screen YES,
- > XLookupString gives 0 characters: ""
- >
- > I'm running a sun 4, SunOS 4.1.2, and X11R5; if your machine or
- > configuration is different, you may get slightly different results, but
- > basically it should be the same.
- >
- > Jim
- > --
- > _ Jim Thompson | Western Geophysical __
- > _| ~- thompson@wg2.waii.com | Exploration Products /\_\
- > \, _} jimt@sugar.neosoft.com | 3600 Briarpark \/_/
- > \( (713) 964-6213 | Houston, TX 77042
- >
- >
- --
- Johannes Grosen
- ISC System Administrator
- grosen@isc.cs.ndsu.NoDak.edu
-