GNU bug report logs - #23163
25.1.50; w32-lwindow-modifier "unset" while running GDB

Previous Next

Full log

View this message in rfc822 format

From: Jussi Lahdenniemi <jussi <at> aprikoodi.fi>
To: martin rudalics <rudalics <at> gmx.at>
Cc: 23163 <at> debbugs.gnu.org, Eli Zaretskii <eliz <at> gnu.org>
Subject: bug#23163: 25.1.50; w32-lwindow-modifier "unset" while running GDB
Date: Thu, 31 Mar 2016 09:34:51 +0300

>> Date: Wed, 30 Mar 2016 19:32:49 +0200
>> From: martin rudalics <rudalics <at> gmx.at>
>>
>> In my .emacs for Windows I have for many years the following settings.
>>
>> (setq w32-pass-lwindow-to-system nil)
>> (setq w32-lwindow-modifier 'hyper)	; lwindow is hyper
>> (global-set-key [(control hyper meta b)] 'break-point-insert)
>>
>> ‘break-point-insert’ is a command that inserts a breakpoint into the
>> *gud-emacs.exe* buffer.  This command works fine in emacs-25 but fails
>> in master when running GDB.  In particular, it fails _after_ focus has
>> shifted to the debugged frame and I shifted it back to the debugger
>> frame.  The command actually executed by C-H-M b is then ‘backward-sexp’
>> which means that apparently ‘w32-lwindow-modifier’ has been unset and my
>> modifier given back to the system.
>>
>> I believe that I have seen similar "unsettings" in other occasions as
>> well but the example given here is the only one I can confirm.

Does it help if you add
(w32-register-hot-key [H-])
after the (global-set-key ...) line in your .emacs?

-- 
Jussi Lahdenniemi

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.