From: Joe <joesmoe10@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Super modifier mapped to super + control
Date: Sun, 23 Nov 2008 20:30:15 -0800 (PST) [thread overview]
Message-ID: <d36fb81b-5b08-4f41-8db6-d1fe1a0499a6@j11g2000yqg.googlegroups.com> (raw)
Hey all,
I'm trying to use the super modifier in some of my key bindings. The
problem is when I hit the super key emacs interprets it as super +
control. For example, when I hit (super t) emacs shows (super control
t). I can bind a key to super + control and it works, but this seems
like a unnecessary hack.
I'm running emacs 23.0.60.1 on Ubuntu 8.10.
xev shows that pressing the super key maps to Super_L.
Starting emacs -q (no init file) has the same behavior.
Any ideas?
next reply other threads:[~2008-11-24 4:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-24 4:30 Joe [this message]
2008-11-24 13:22 ` Super modifier mapped to super + control Xah Lee
2008-11-24 18:24 ` Joe
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=d36fb81b-5b08-4f41-8db6-d1fe1a0499a6@j11g2000yqg.googlegroups.com \
--to=joesmoe10@gmail.com \
--cc=help-gnu-emacs@gnu.org \
/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).