unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Pascal Bourguignon <spam@mouse-potato.com>
Subject: Re: Problems Using Hyper Key modifier
Date: Sat, 24 Sep 2005 05:38:19 +0200	[thread overview]
Message-ID: <873bnvp238.fsf@thalassa.informatimago.com> (raw)
In-Reply-To: mailman.8312.1127526997.20277.help-gnu-emacs@gnu.org

Tim Johnson <tim@johnsons-web.com> writes:

> Hello:
>
> I would like to map my TAB key to the hyper key modifier.
>
> After running the following command to map the TAB key to Hyper key:
> xmodmap -e "keycode 23 = Hyper_L"
>
> xev tells me that keycode 23 is Hyper_L, but
> <blush> I find that that c-h k <ret>
> TAB-n only recognizes the "n". 
> The TAB=>Hyper_L key is not recognized as a modifier

Did you press both keys simultaneously? TAB-down n-down n-up TAB-up
Did you list Hyper_L as a modifier?

> What else do I need to do? 
>
> NOTE: There are many examples found by Google that show how to map
> caps_lock to hyper, but I have already successfully mapped caps_lock to
> control_L.
>
> Also, attempts to map control_r (keycode 109) to Hyper_R fail
> as well.

Put something like:

clear Shift
clear Lock
clear Control
clear Mod1
clear Mod2
clear Mod3
clear Mod4
clear Mod5

! In order of bits: 
add    Shift   = Shift_L     Shift_R
add    Lock    = Caps_Lock
add    Control = Control_L   Control_R
add    Mod1    = Alt_L       Alt_R
add    Mod2    = Num_Lock
add    Mod3    = Super_L     Super_R
add    Mod4    = Meta_L      Meta_R
add    Mod5    = Hyper_L     Hyper_R     

in your ~/.xmodmap


-- 
__Pascal Bourguignon__                     http://www.informatimago.com/
Cats meow out of angst
"Thumbs! If only we had thumbs!
We could break so much!"

       reply	other threads:[~2005-09-24  3:38 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.8312.1127526997.20277.help-gnu-emacs@gnu.org>
2005-09-24  3:38 ` Pascal Bourguignon [this message]
2005-09-24 16:51   ` Problems Using Hyper Key modifier Tim Johnson
2005-09-24  1:56 Tim Johnson

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=873bnvp238.fsf@thalassa.informatimago.com \
    --to=spam@mouse-potato.com \
    /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).