unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stephen Berman <stephen.berman@gmx.net>
To: Po Lu <luangruo@yahoo.com>
Cc: 54289@debbugs.gnu.org
Subject: bug#54289: 29.0.50; Emacs ignores xmodmap Super_L assignment
Date: Tue, 08 Mar 2022 12:40:24 +0100	[thread overview]
Message-ID: <87bkygu0yf.fsf@gmx.net> (raw)
In-Reply-To: <87wnh4k88p.fsf@yahoo.com> (Po Lu's message of "Tue, 08 Mar 2022 19:13:10 +0800")

On Tue, 08 Mar 2022 19:13:10 +0800 Po Lu <luangruo@yahoo.com> wrote:

> Stephen Berman <stephen.berman@gmx.net> writes:
>
>> You mean forward slash and backslash?  I.e. mod4 subsumes the Super_L
>> and Menu keysyms?
>
> No, just forward slash.
>
>> I tried with all three remove mappings and also with just the first two,
>> but in both cases nothing changed, i.e., typing Super_L (the Windows key
>> on my keyboard) still produced nothing in emacs-29 (non-pgtk build).
>> Same in Firefox.  FWIW evaluating `xmodmap .Xmodmap' gives this output
>> (both with the lines you suggested adding and without them):
>>
>> xmodmap: .Xmodmap:16: bad keysym in remove modifier list 'Caps_Lock', no
>> corresponding keycodes
>> xmodmap: .Xmodmap:18: bad keysym target keysym 'Caps_Lock', no corresponding
>> keycodes
>> xmodmap: .Xmodmap:49: bad keysym target keysym 'Super_L', no corresponding
>> keycodes
>> xmodmap:  .Xmodmap:52:  bad keysym target keysym 'Menu', no corresponding keycodes
>> xmodmap:  4 errors encountered, aborting.
>>
>> Nevertheless, only the Super_L mapping fails in emacs-29 (and Firefox).
>
> Thanks, then please run GDB, and add a breakpoint like this:
>
>   (gdb) break xterm.c:12731
>
> It should then print something along the lines of
>
>   Breakpoint N at 0x505332: file xterm.c, line 12731.
>
> At this point, say:
>
>   (gdb) condition N rec->map->modmap[xev->detail] != 0
>   (gdb) commands
>   Type commands for breakpoint(s) 3, one per line.
>   End with a line saying just "end".
>   >p rec->map->modmap[xev->detail]
>   >c
>   >end
>
> where N is the number of the breakpoint that was printed above, then run
> Emacs like this:
>
>   (gdb) run -q -xrm 'Emacs.useXIM: false'
>
> Press the left super key, and show the output.  Thanks.

My xterm.c is not quite up to date, so I adjusted the breakpoint:

(gdb) break xterm.c:12547
Breakpoint 3 at 0x55b4c9: file /home/steve/src/emacs/emacs-master/src/xterm.c, line 12547.
(gdb) condition 3 rec->map->modmap[xev->detail] != 0
(gdb) commands
Type commands for breakpoint(s) 3, one per line.
End with a line saying just "end".
>p rec->map->modmap[xev->detail]
>c
>end
(gdb) run -q -xrm 'Emacs.useXIM: false'
Starting program: /home/steve/build/emacs-master/src/emacs -q -xrm 'Emacs.useXIM: false'
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
[New Thread 0x7fffea505640 (LWP 10837)]
[New Thread 0x7fffe9af7640 (LWP 10838)]
[New Thread 0x7fffe8f9a640 (LWP 10839)]
[New Thread 0x7fffdbfff640 (LWP 10840)]
[Thread 0x7fffdbfff640 (LWP 10840) exited]
[New Thread 0x7fffdbfff640 (LWP 10841)]
[New Thread 0x7fffdb66f640 (LWP 10842)]
[Thread 0x7fffdbfff640 (LWP 10841) exited]
[Thread 0x7fffdb66f640 (LWP 10842) exited]
[New Thread 0x7fffdb66f640 (LWP 10843)]
[New Thread 0x7fffdbfff640 (LWP 10844)]
[Thread 0x7fffdb66f640 (LWP 10843) exited]
[Thread 0x7fffdbfff640 (LWP 10844) exited]

Thread 1 "emacs" hit Breakpoint 3, handle_one_xevent (dpyinfo=dpyinfo@entry=0xd586e0, event=event@entry=0x7fffffffd410, finish=finish@entry=0xaac980 <current_finish>, hold_quit=0x7fffffffd660) at /home/steve/src/emacs/emacs-master/src/xterm.c:12549
warning: Source file is more recent than executable.
12549			  if (rec->map->modmap && rec->map->modmap[xev->detail])
$1 = 64 '@'
[Thread 0x7fffe8f9a640 (LWP 10839) exited]

The GDB session is still running; do you want any further output?

Steve Berman





  reply	other threads:[~2022-03-08 11:40 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07 11:36 bug#54289: 29.0.50; Emacs ignores xmodmap Super_L assignment Stephen Berman
2022-03-07 15:24 ` Lars Ingebrigtsen
2022-03-07 15:53   ` Stephen Berman
2022-03-07 15:59     ` Lars Ingebrigtsen
2022-03-07 16:14       ` Stephen Berman
2022-03-08  0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08  0:39   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08  8:52     ` Stephen Berman
2022-03-08 10:10       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 10:21         ` Stephen Berman
2022-03-08 10:28           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 10:52             ` Stephen Berman
2022-03-08 11:13               ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 11:40                 ` Stephen Berman [this message]
2022-03-08 11:51                   ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 12:03                     ` Stephen Berman
2022-03-08 12:59                       ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 13:24                         ` Stephen Berman
2022-03-08 13:35                           ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-03-08 13:55                             ` Stephen Berman
2022-03-08 13:52                           ` Andreas Schwab
2022-03-08 14:02                             ` Stephen Berman
2022-03-08 14:21                               ` Andreas Schwab

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87bkygu0yf.fsf@gmx.net \
    --to=stephen.berman@gmx.net \
    --cc=54289@debbugs.gnu.org \
    --cc=luangruo@yahoo.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).