From: yuan@cs.umd.edu
Subject: Re: M-TAB already used by KDE
Date: 20 Dec 2002 18:29:06 -0500 [thread overview]
Message-ID: <87n0n09sn1.fsf@genesys.cs.umd.edu> (raw)
In-Reply-To: 1mznr0gz9l.fsf@Tempo.Update.UU.SE
Fredrik Staxeng <fstx+u@update.uu.se> writes:
> >Fredrik Staxeng <fstx+u@update.uu.se> writes:
> ...
> I found a picture of the space-cadet keyboard on the web:
>
> http://screenshots.sourceforge.net/misc/SpaceCadet1.jpg
>
> The web page says that this was used with LMI machines as well. It has
> Shift, Ctrl, Meta, Super, Hyper, Greek and Top. The X keyboard model
> is definitely not enough to support this keyboard.
>
> But anyway, since there is no specific name for mod5 there is no way
> to use five distinct modifiers (in addition to Shift and Ctlr) with
> Emacs, is there?
>
> With universal UTF-8 support just around the corner, people might
> want to put real alphas etc in their Tex/Nroff documents. Thus a
> Greek modifier is needed :-)
I have setup my pc101 keyboard to have Emacs recognized all Escape, Meta,
Alt, Control, Super, Hyper, Shift, etc etc. Below is my ~/.Xmodmap, which
makes my keyboard look like this:
[Control]
[Shift] .....................................[Shift]
[Fn/Multi] [Hyper] [Meta] [Space] [Alt] [Super]
I hope everyone adopt this map so there is nonzero chance that I'll still
be able to function when forced to use others' keyboard. :)
______________________________________________________________________________
clear Control
clear Lock
clear mod1
clear mod2
clear mod3
clear mod4
clear mod5
keysym Control_L = Hyper_L
keysym Control_R = Super_R
keysym Alt_L = Meta_L
keysym Meta_R = Alt_R
keysym Caps_Lock = Control_L
! make the thinkpad Fn key double as multi key
keycode 227 = Multi_key
add Control = Control_L
add Lock = Caps_Lock
add mod1 = Meta_L Meta_R Multi_key
add mod2 = Hyper_L Hyper_R
add mod3 = Num_Lock
add mod4 = Alt_L Alt_R
add mod5 = Super_L Super_R Scroll_Lock
next prev parent reply other threads:[~2002-12-20 23:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 21:12 M-TAB already used by KDE Marcel Schmittfull
2002-12-16 21:13 ` David Kastrup
2002-12-16 21:39 ` Marcel Schmittfull
2002-12-16 21:54 ` Benjamin Lewis
[not found] ` <87bs3l2fgk.fsf@kuntu.zangpo.org>
2002-12-17 10:46 ` Kai Großjohann
[not found] ` <87u1hcyseg.fsf@kuntu.zangpo.org>
2002-12-18 17:35 ` Kai Großjohann
2002-12-17 21:53 ` Benjamin Lewis
2002-12-21 1:11 ` Big Bird
2002-12-18 15:23 ` Marcel Schmittfull
2002-12-18 17:12 ` Kai Großjohann
2002-12-18 18:59 ` asoyeur
2002-12-19 11:00 ` Kester Clegg
2002-12-16 21:32 ` Mark Mynsted
2002-12-16 21:43 ` Marcel Schmittfull
2002-12-17 7:42 ` Roman Belenov
2002-12-17 9:19 ` Kai Großjohann
2002-12-18 18:29 ` Fredrik Staxeng
2002-12-18 20:26 ` Kai Großjohann
2002-12-18 21:46 ` Fredrik Staxeng
2002-12-19 7:32 ` Kai Großjohann
2002-12-19 11:59 ` Fredrik Staxeng
2002-12-19 14:25 ` Kai Großjohann
2002-12-19 15:36 ` Fredrik Staxeng
2002-12-20 18:42 ` Kai Großjohann
2002-12-20 21:24 ` Fredrik Staxeng
2002-12-20 22:04 ` Benjamin Lewis
2002-12-20 23:29 ` yuan [this message]
2002-12-21 12:55 ` Kai Großjohann
2002-12-21 13:57 ` Fredrik Staxeng
2002-12-17 18:02 ` Jochem Huhmann
2002-12-19 13:26 ` Carsten Dominik
-- strict thread matches above, loose matches on Subject: below --
2002-12-17 18:52 Marcel Schmittfull
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=87n0n09sn1.fsf@genesys.cs.umd.edu \
--to=yuan@cs.umd.edu \
/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.
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).