From: Po Lu via "Bug reports for GNU Emacs, the Swiss army knife of text editors" <bug-gnu-emacs@gnu.org>
To: bg.jheng@gmail.com
Cc: 54889@debbugs.gnu.org
Subject: bug#54889: 29.0.50; shift keys can't function when using setxkbmap with custom_symbol in gnome
Date: Wed, 13 Apr 2022 08:04:12 +0800 [thread overview]
Message-ID: <8735ihx30j.fsf@yahoo.com> (raw)
In-Reply-To: <CAEFYKcN4BV9ATjwwMqAsd2WVY3KXmN8hMBbgyVFyZOityGE=ag@mail.gmail.com> (bg jheng's message of "Tue, 12 Apr 2022 15:10:26 +0000")
bg.jheng@gmail.com writes:
> all keys work normally,
> my extra key level and group are working fine,
> but Shift_L, Shift_R are no function when i using emacs -q in v29 .
> i saw `H-_ is indefined` in minibuffer but no any letter inserted when i tried to input any capital letter .
>
> finally, i found it can input capital letter, if i removed modifier_map of shift keys:
> in xkb_symbols file:
> // modifier_map Shift { <LFSH> };
> // modifier_map Shift { <RTSH> };
> // modifier_map Shift { Shift_L, Shift_R };
>
> my xkb files in here:
> https://drive.google.com/file/d/19_tcP8VSeUYgG9f4zkGEbavbaBOwOLso/view?usp=sharing
>
> and using cmd:
> setxkbmap -model pc104 -layout us -symbols mysymbol
> or
> xkbcomp .config/xkb/myxkb_keymap.xkb $DISPLAY
>
> now, emacs v29 shift key plus any letter can be inputed capital letter.
>
> because the same xkb keymap is woring normally in emacs 27, 28,
> so i am wonder if there is any difference in mechanisms of keymap in emacs v29?
A great deal has changed under the hood.
Would you please show the output of `xmodmap' with the shift key mapping
rules that you removed installed?
Thanks in advance.
next prev parent reply other threads:[~2022-04-13 0:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 15:10 bug#54889: 29.0.50; shift keys can't function when using setxkbmap with custom_symbol in gnome bg.jheng
2022-04-13 0:04 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors [this message]
[not found] ` <CAEFYKcNtvjtsF2EF6qNJfsM+1kPbkyBTNox_Kc10v0uy42Mf3g@mail.gmail.com>
2022-04-13 3:24 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <CAEFYKcO8TxmUOopUMnmbm0ZQM5GtfG9P0hEytpYAge==r0p9pA@mail.gmail.com>
[not found] ` <877d7tvatx.fsf@yahoo.com>
[not found] ` <CAEFYKcMUtWiCg=oSgNdhrNok-z_V2rBnR1pyeiNsbCtjHsk4uA@mail.gmail.com>
2022-04-14 0:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-14 11:48 ` bg.jheng
2022-04-14 13:18 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-14 22:56 ` bg.jheng
2022-04-15 0:49 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-04-15 3:37 ` bg.jheng
2022-04-15 4:28 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
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=8735ihx30j.fsf@yahoo.com \
--to=bug-gnu-emacs@gnu.org \
--cc=54889@debbugs.gnu.org \
--cc=bg.jheng@gmail.com \
--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).