From: Steve Greenburg <beethoven3322@hotmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "44456@debbugs.gnu.org" <44456@debbugs.gnu.org>
Subject: bug#44456: Windows10 doesn't allow either windows keys as hyper?
Date: Thu, 5 Nov 2020 17:05:10 +0000 [thread overview]
Message-ID: <MWHPR13MB1758454734DDAFCC9F494DC9A3EE0@MWHPR13MB1758.namprd13.prod.outlook.com> (raw)
In-Reply-To: <83lfffagmi.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1104 bytes --]
The documentation for w32-register-hotkey says it is [h-] so I used that. Using [H-] does work as long as I change the variable before calling w32-register-hot-key like so:
(setq w32-lwindow-modifier 'hyper)
(w32-register-hot-key [H-])
(setq w32-pass-lwindow-to-system nil)
Thanks.
________________________________
From: Eli Zaretskii <eliz@gnu.org>
Sent: Thursday, November 5, 2020 4:54 PM
To: Steve Greenburg <beethoven3322@hotmail.com>
Cc: 44456@debbugs.gnu.org <44456@debbugs.gnu.org>
Subject: Re: bug#44456: Windows10 doesn't allow either windows keys as hyper?
> From: Steve Greenburg <beethoven3322@hotmail.com>
> CC: "44456@debbugs.gnu.org" <44456@debbugs.gnu.org>
> Date: Thu, 5 Nov 2020 16:48:12 +0000
>
> I believe it's still a bug because I can't get the left windows key to function as hyper without first making it
> function as super. Thus if I execute the following code I get nothing:
>
> (setq w32-lwindow-modifier 'hyper)
> (setq w32-pass-lwindow-to-system nil)
> (w32-register-hot-key [h-])
The Hyper modifier is [H-], not [h-]. Does H- work for you?
[-- Attachment #2: Type: text/html, Size: 2077 bytes --]
next prev parent reply other threads:[~2020-11-05 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 21:44 bug#44456: Windows10 doesn't allow either windows keys as hyper? Steve Greenburg
2020-11-05 13:35 ` Eli Zaretskii
2020-11-05 16:48 ` Steve Greenburg
2020-11-05 16:54 ` Eli Zaretskii
2020-11-05 17:05 ` Steve Greenburg [this message]
2020-11-05 17:47 ` Eli Zaretskii
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=MWHPR13MB1758454734DDAFCC9F494DC9A3EE0@MWHPR13MB1758.namprd13.prod.outlook.com \
--to=beethoven3322@hotmail.com \
--cc=44456@debbugs.gnu.org \
--cc=eliz@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).