public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk> To: cygwin-xfree@cygwin.com Cc: david@adboyd.com Subject: Re: cygwin and xwin and super and hyper Date: Thu, 20 Jun 2013 10:55:00 -0000 [thread overview] Message-ID: <51C2DF91.1010605@dronecode.org.uk> (raw) In-Reply-To: <m9hi61x9bxl5.fsf@W0144758.usac.mmm.com> On 19/06/2013 22:27, J. David Boyd wrote: > I can get my capslock key to be super with the command line 'setxkbmap -option > caps:super', but I can't get 'setxkbmap -option altwin:hyper_win' to do > anything. > > Running 'setxkbmap -print' shows both options as being set, but the win keys > still act as the win key. > > Is there something else I need to do so windows lets go of these keys? Yes. Again, let me refer you to [1]. The operative sentence is: > (Note that mapping the Windows keys to hyper also requires the -keyhook > option, so that the X server sees those keys before the Windows shell) One thing I failed to mention there is that without any keymap options the keymap should give you super on the windows keys, but you will still need -keyhook X server option to enable the X server to see the key. [1] http://cygwin.com/ml/cygwin/2012-03/msg00427.html -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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/
next prev parent reply other threads:[~2013-06-20 10:55 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 [this message] 2013-06-21 15:56 ` J. David Boyd 2013-06-24 14:05 ` Jon TURNEY 2013-06-24 18:08 ` J. David Boyd
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=51C2DF91.1010605@dronecode.org.uk \ --to=jon.turney@dronecode.org.uk \ --cc=cygwin-xfree@cygwin.com \ --cc=david@adboyd.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: linkBe 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).