From: Angelina Carlton <brat@magma.ca>
Subject: Re: emacs-snapshot keybinding problem
Date: Sat, 31 Dec 2005 10:41:22 -0500 [thread overview]
Message-ID: <87hd8p5l5p.fsf@magma.ca> (raw)
In-Reply-To: <3c110c9e9c722c8b8843bee0bea47a2f@Web.DE> (Peter Dyballa's message of "Sat, 31 Dec 2005 00:52:47 +0100")
Peter Dyballa <Peter_Dyballa@Web.DE> writes:
>
> keycode 115 = Hyper
> add Mod4 = Hyper
> keycode 115 = super
> add Mod5 = super
Ok, for this system it complains that Hyper and super are not valid
keysyms so this is my ~/.xmodmaprc
,----
| keycode 182 = F13
| keycode 183 = F14
| keycode 184 = F15
| keycode 93 = F16
| keycode 115 = Hyper_L
| clear Mod3
| add Mod3 = Hyper_L
| keycode 116 = Super_R
| clear Mod4
| add Mod4 = Super_R
`----
xmodmap -pm:
,----
| xmodmap: up to 3 keys per modifier, (keycodes in parentheses):
| shift Shift_L (0x32), Shift_R (0x3e)
| lock
| control Control_L (0x25), Control_L (0x42), Control_R (0x6d)
| mod1 Alt_L (0x40), Alt_R (0x71)
| mod2 Num_Lock (0x4d)
| mod3 Hyper_L (0x73)
| mod4 Super_R (0x74)
| mod5 Scroll_Lock (0x77)
`----
So my function keys now go all the way up to F16 :-) and I have OPTL set
to Hyper_L and OPTR set to Super_R, I now need to
learn the syntax to bind something to the Super and Hyper keys
(global-set-key [(hyper q)] 'some-function) does not work.
> You probably know what xmodmap -pm shows? And you probably already
> learned that you can re-map the keys in X11 at once, without re-boot,
> log-off and -in, shutting X11 down and re-launching it?
>
I am just using xmodmap ~/.xmodmaprc to "source" this file.
Incidentally these function keys still get overwritten in emacs22, I have
not tried to address this yet because as you pointed out, my
key mappings were incorrect to begin with, even in emacs21 so one step at
a time I suppose :)
--
-----Angelina Carlton-----
orchid on irc.freenode.net
brat@magma.ca
web:bzgirl.bakadigital.com
--------------------------
next prev parent reply other threads:[~2005-12-31 15:41 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.20812.1135883611.20277.help-gnu-emacs@gnu.org>
2005-12-30 4:49 ` emacs-snapshot keybinding problem Stefan Monnier
2005-12-30 14:21 ` Angelina Carlton
2005-12-30 15:45 ` Peter Dyballa
2005-12-30 18:31 ` Angelina Carlton
2005-12-30 23:52 ` Peter Dyballa
2005-12-31 15:41 ` Angelina Carlton [this message]
2005-12-31 17:21 ` Peter Dyballa
2006-01-01 18:04 ` Angelina Carlton
2006-01-01 18:57 ` Peter Dyballa
2006-01-02 20:24 ` Angelina Carlton
2006-01-03 12:58 ` Peter Dyballa
2006-01-03 22:49 ` Angelina Carlton
2006-01-03 23:52 ` Peter Dyballa
2006-01-04 21:51 ` Angelina Carlton
2006-01-04 22:48 ` Peter Dyballa
2006-01-06 5:08 ` Ian Zimmerman
2006-01-06 18:17 ` Angelina Carlton
[not found] ` <mailman.21417.1136411578.20277.help-gnu-emacs@gnu.org>
2006-01-05 10:57 ` Romain Francoise
2006-01-05 14:05 ` Angelina Carlton
2006-01-02 16:36 ` Stefan Monnier
2006-01-04 21:43 ` Angelina Carlton
2005-12-29 19:11 Angelina Carlton
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=87hd8p5l5p.fsf@magma.ca \
--to=brat@magma.ca \
/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).