From: "Elia Nolz" <gnu-emacs@lycheese.org>
To: "Yuuki Harano" <masm+emacs@masm11.me>
Cc: 48136@debbugs.gnu.org
Subject: bug#48136: 28.0.50; [feature/pgtk] ISO_Level5_Shift broken
Date: Thu, 20 May 2021 15:28:49 +0200 [thread overview]
Message-ID: <00dafb80-759e-43cb-96f3-15dfa8b4392f@www.fastmail.com> (raw)
In-Reply-To: <20210520.200227.525100289182643979.masm@luna.pink.masm11.me>
[-- Attachment #1: Type: text/plain, Size: 1087 bytes --]
On Thu, May 20, 2021, at 13:02, Yuuki Harano wrote:
> Key events are handled in key_press_event() in pgtkterm.c.
> I think `keysym` contains a character code, which is already
> interpreted.
I stepped through the code with gdb and watched the keysym values.
I observed the following values for keysym in this order when pressing "C-L3-i" (sends "C-{") (working case):
65507 (state goes to 4 --> state to 0 and modifiers to 4)
65027 (state becomes 132 --> modifiers becomes 132 and state 128)
123 (no changes to state and modifiers)
65515 (should be me using Super+o to switch workspaces in xmonad)
And these for the non working case "C-L3-n" (which sends "(" and should send "C-("):
65507 (state to 4 --> state to 0 and modifiers to 4)
65027 (both state and modifiers become 0)
65515
I was unable to get the keysym of the key itself in the non-working cases.
Used breakpoints in pgtkterm.c:
5669
5687
5701
5710
5731
5809
5860
5876
I sadly do not know enough C to understand why this happens. Does this help you at all? Any further information I could provide that would be helpful?
[-- Attachment #2: Type: text/html, Size: 1715 bytes --]
next prev parent reply other threads:[~2021-05-20 13:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 9:34 bug#48136: 28.0.50; [feature/pgtk] ISO_Level5_Shift broken Elia Nolz
2021-05-08 11:50 ` Elia Nolz
2021-05-09 10:17 ` Yuuki Harano
2021-05-09 10:47 ` Elia Nolz
2021-05-20 9:30 ` Elia Nolz
2021-05-20 11:02 ` Yuuki Harano
2021-05-20 13:28 ` Elia Nolz [this message]
2021-05-20 16:02 ` Yuuki Harano
2021-05-20 16:58 ` Elia Nolz
2021-05-21 6:57 ` Yuuki Harano
2021-05-21 8:22 ` Elia Nolz
2021-05-21 9:56 ` Yuuki Harano
2021-06-09 9:21 ` Elia Nolz
2021-06-24 8:52 ` Elia Nolz
2021-06-25 12:05 ` Yuuki Harano
2021-10-01 15:09 ` Elia Nolz
2022-07-01 11:13 ` Lars Ingebrigtsen
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=00dafb80-759e-43cb-96f3-15dfa8b4392f@www.fastmail.com \
--to=gnu-emacs@lycheese.org \
--cc=48136@debbugs.gnu.org \
--cc=masm+emacs@masm11.me \
/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).