From: Mambo Levis <mambo.levis@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: "24453@debbugs.gnu.org" <24453@debbugs.gnu.org>
Subject: bug#24453: Hyper and super keys don't work in some branches
Date: Sat, 17 Sep 2016 11:52:43 +0000 (UTC) [thread overview]
Message-ID: <686206770.114660.1474113163993@mail.yahoo.com> (raw)
In-Reply-To: <83fuoy50aj.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1878 bytes --]
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.
[-- Attachment #2: Type: text/html, Size: 5817 bytes --]
next prev parent reply other threads:[~2016-09-17 11:52 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 [this message]
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
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=686206770.114660.1474113163993@mail.yahoo.com \
--to=mambo.levis@gmail.com \
--cc=24453@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 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.