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

Previous Next

Full log

Message #8 received at 23163 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: martin rudalics <rudalics <at> gmx.at>, Jussi Lahdenniemi <jussi <at> aprikoodi.fi>
Cc: 23163 <at> debbugs.gnu.org
Subject: Re: bug#23163: 25.1.50; w32-lwindow-modifier "unset" while running GDB
Date: Wed, 30 Mar 2016 21:23:55 +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.

Probably due to changes in 97d7a0b.  Jussi, could you please take a
look?

Previous Next

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