public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: david@adboyd.com (J. David Boyd)
To: cygwin-xfree@cygwin.com
Subject: Re: cygwin and xwin and super and hyper
Date: Mon, 24 Jun 2013 18:08:00 -0000 [thread overview]
Message-ID: <m9hitxkn5qlr.fsf@W0144758.usac.mmm.com> (raw)
In-Reply-To: <51C8521B.9050507@dronecode.org.uk>
Jon TURNEY <jon.turney@dronecode.org.uk> writes:
> On 21/06/2013 16:56, J. David Boyd wrote:
>> Jon TURNEY writes:
>>> On 19/06/2013 22:27, J. David Boyd wrote:
>>
>> All perfect so far.
>>
>> So, when I start up emacs, and press C-h k, then, for example, Capslock-d,
>> (hyper-d) I get 'H-d is undefined'. Yeah.
>>
>> Then I press C-h k, then Left-Win-d, (super-d), I get 'H-d is undefined', and
>> not 's-d is undefined', which is what I expected to see.
>>
>> Any ideas how I might resolve this?
>
> Looking at the xev output for Hyper-d and Super-d, it seems they have the same
> state (modifier) value.
>
> This is because xkeyboard-config seems to place super and hyper on the same
> modifier, mod4, as can be seen looking at the output of 'xmodmap -pm'
>
>> $ xmodmap -pm
>> xmodmap: up to 5 keys per modifier, (keycodes in parentheses):
>>
>> shift Shift_L (0x32), Shift_R (0x3e)
>> lock
>> control Control_L (0x25), Control_R (0x6d)
>> mod1 Alt_L (0x40), Alt_R (0x74), Meta_L (0x9c)
>> mod2 Num_Lock (0x4d)
>> mod3
>> mod4 Hyper_L (0x42), Super_L (0x73), Super_R (0x75), Super_L (0x7f), Hyper_L (0x80)
>> mod5 Mode_switch (0x8), ISO_Level3_Shift (0x7c)
>
> And it seems that emacs only looks at the modifier state, not the actual
> proceeding keypress.
>
> A workaround for this is to move Hyper_L to the unused mod3 modifier.
>
>> $ xmodmap -e "remove mod4 = Hyper_L"
>>
>> $ xmodmap -e "add mod3 = Hyper_L"
>>
>> $ 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_R (0x6d)
>> mod1 Alt_L (0x40), Alt_R (0x74), Meta_L (0x9c)
>> mod2 Num_Lock (0x4d)
>> mod3 Hyper_L (0x42), Hyper_L (0x80)
>> mod4 Super_L (0x73), Super_R (0x75), Super_L (0x7f)
>> mod5 Mode_switch (0x8), ISO_Level3_Shift (0x7c)
>
> It's probably a bug that this doesn't work as expected, but I'm not sure in what.
Thanks, that just what I did, and now it works fine.
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
prev parent reply other threads:[~2013-06-24 18:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-19 21:27 J. David Boyd
2013-06-20 10:55 ` Jon TURNEY
2013-06-21 15:56 ` J. David Boyd
2013-06-24 14:05 ` Jon TURNEY
2013-06-24 18:08 ` J. David Boyd [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m9hitxkn5qlr.fsf@W0144758.usac.mmm.com \
--to=david@adboyd.com \
--cc=cygwin-xfree@cygwin.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).