From: Tim Johnson <tim@johnsons-web.com>
Subject: Problems Using Hyper Key modifier
Date: Fri, 23 Sep 2005 17:56:09 -0800 [thread overview]
Message-ID: <20050924015609.GA10968@johnsons-web.com> (raw)
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
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.
TIA
tim
--
Tim Johnson <tim@johnsons-web.com>
http://www.alaska-internet-solutions.com
next reply other threads:[~2005-09-24 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-24 1:56 Tim Johnson [this message]
[not found] <mailman.8312.1127526997.20277.help-gnu-emacs@gnu.org>
2005-09-24 3:38 ` Problems Using Hyper Key modifier Pascal Bourguignon
2005-09-24 16:51 ` 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=20050924015609.GA10968@johnsons-web.com \
--to=tim@johnsons-web.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).