all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Robert Cochran <robert-emacs@cochranmail.com>
Cc: "24453@debbugs.gnu.org" <24453@debbugs.gnu.org>,
	Mambo Levis <mambo.levis@gmail.com>
Subject: bug#24453: Hyper and super keys don't work in some branches
Date: Wed, 21 Sep 2016 13:07:32 -0400	[thread overview]
Message-ID: <CAM-tV-_D=sSE1r3h17R9RZ2vQAXOG+a5AW18DCYWB+M0ExihnQ@mail.gmail.com> (raw)
In-Reply-To: <87oa3ikvfz.fsf@cochranmail.com>

On Tue, Sep 20, 2016 at 7:22 PM, Robert Cochran
<robert-emacs@cochranmail.com> wrote:
> I eventually managed to get it to work from the official Emacs 25.1
> release, so I think that the problem has been fixed.
>
> This is the form I used:
>
> (when (eq system-type 'windows-nt)
>   (setq w32-pass-lwindow-to-system nil)
>   (setq w32-pass-apps-to-system nil)
>   (setq w32-lwindow-modifier 'super)
>   ;; My laptop does not have a right super, so I used the
>   ;; 'apps'/'menu' key instead.
>   (setq w32-apps-modifier 'hyper))
>
> Also note that even still, Windows still ate a lot of the attempted
> super key combos, even those that didn't look like they did anything
> (s-z, for example). I know that `s-w` was passed to Emacs, as well as
> most of the symbol characters ('[', ';', etc...).
>

Perhaps this is some OS difference? `s-w` did not get passed through
for me, hardly any letters did. I see the same behaviour with 24.5 and
25.1.

This is what "System Information" tells me:
OS Name    Microsoft Windows 10 Home
Version    10.0.14393 Build 14393

Here are all the unshifted keys that got passed through:

s-y is undefined
s-n is undefined
s-[ is undefined
s-] is undefined
s-. is undefined
s-` is undefined
s-- is undefined
s-; is undefined
s-' is undefined
s-\ is undefined

All the other unshifted keys were blocked.





  parent reply	other threads:[~2016-09-21 17:07 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-16 22:44 bug#24453: Hyper and super keys don't work in some branches Mambo Levis
2016-09-17  7:33 ` Eli Zaretskii
     [not found]   ` <1812033429.98968.1474103814634@mail.yahoo.com>
2016-09-17  9:43     ` Eli Zaretskii
2016-09-17 11:52       ` Mambo Levis
2016-09-17 12:05         ` Eli Zaretskii
2016-09-17 12:26           ` Mambo Levis
2016-09-17 17:48           ` Robert Cochran
2016-09-17 17:56             ` Mambo Levis
2016-09-20 18:53               ` Mambo Levis
2016-09-20 23:22                 ` Robert Cochran
2016-09-21  8:55                   ` Mambo Levis
2016-09-21 14:44                     ` Eli Zaretskii
2016-09-21 16:42                       ` Mambo Levis
2016-09-21 17:02                         ` Eli Zaretskii
2016-09-21 17:17                           ` Mambo Levis
2016-09-21 17:45                             ` Mambo Levis
2016-09-21 17:45                             ` Eli Zaretskii
2016-09-21 18:08                               ` Mambo Levis
2016-09-21 18:27                                 ` Eli Zaretskii
2016-09-21 18:43                                   ` Mambo Levis
2016-09-21 19:10                                     ` Eli Zaretskii
2016-09-23  1:53                                       ` Mambo Levis
2016-09-23 13:23                                         ` Mambo Levis
2016-09-23 14:12                                           ` Mambo Levis
2016-09-23 15:09                                             ` Eli Zaretskii
2016-09-21 14:38                   ` Eli Zaretskii
2016-09-21 17:07                   ` Noam Postavsky [this message]
2016-09-17 17:27 ` Chris Zheng

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='CAM-tV-_D=sSE1r3h17R9RZ2vQAXOG+a5AW18DCYWB+M0ExihnQ@mail.gmail.com' \
    --to=npostavs@users.sourceforge.net \
    --cc=24453@debbugs.gnu.org \
    --cc=mambo.levis@gmail.com \
    --cc=robert-emacs@cochranmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.