bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#24453: Hyper and super keys don't work in some branches


From: Mambo Levis
Subject: bug#24453: Hyper and super keys don't work in some branches
Date: Sat, 17 Sep 2016 11:52:43 +0000 (UTC)

This is the piece of code in my config related to the keys:

;; windows setup and environment vars
(when (eq system-type 'windows-nt)
  (setq w32-pass-lwindow-to-system nil)
  (setq w32-pass-rwindow-to-system nil)
  ;;(setq w32-pass-apps-to-system nil)
  (setq w32-lwindow-modifier 'hyper)   ; Left Windows key
  (setq w32-rwindow-modifier 'super)   ; Right Windows key
  )

 >> Or are you saying that on older versions the problem didn't exist?
No, I don't have access to other windows version than 10.

Also notice that the problem also exists when I used the pretest (binaries) of version 25, it means that the problem is not located 
in my build process. 

It is also important to remark that the official released version 24.5 (binaries) works without problem. 


On Saturday, September 17, 2016 11:43 AM, Eli Zaretskii <eliz@gnu.org> wrote:


> Date: Sat, 17 Sep 2016 09:16:54 +0000 (UTC)
> From: Mambo Levis <mambo.levis@gmail.com>
>
> The point is that I don't change anything in my config and the two keys work when I build
> emacs from master.
>
> When I build any other branch, the super and hyper keys didn't work. As I told you, I do not change
> my config.

I see.  However, this doesn't help in understanding the nature of the
problem.  Please describe your customizations related to these keys:
what do you put in your init file to get them working?

> My test are made in Windows 10.
>
> Do you use any special flag or something special when you build from a branch?

No.


> Did you build it in Windows 10?


No, I have no access to Windows 10.  But it is not clear to me that
this is specific to the Windows version.  Or are you saying that on
older versions the problem didn't exist?

And please keep the bug address on the CC list, so that this
discussion gets recorded by the bug tracker.

Thanks.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]