unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: bg.jheng@gmail.com
To: Po Lu <luangruo@yahoo.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: Fri, 15 Apr 2022 03:37:40 +0000	[thread overview]
Message-ID: <CAEFYKcOZFEjiYk_u=+gn+TW8T6XPSVOd5bRfettMMKrDYGx-qg@mail.gmail.com> (raw)
In-Reply-To: <87ilrbrx07.fsf@yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 1075 bytes --]

I serched my map and found no config part  had Hyper for virtualModifier ,
but i found Hyper_R config in symbols  <RTSH>  in group 2,
after changed to Shift_R,
i can inser capital letter in emacs 29.
old:   key <RTSH> {  [         Shift_R, Shift_R, U2E9D] ,[ Hyper_R ] };
new:   key <RTSH> {  [         Shift_R, Shift_R, U2E9D] ,[ Shift_R ] };

I don't know why cause that,
since that is not belong parts of emacs,
I feel so sorry any where for this report let you be troubled.

Anyway, thanks you for your help.

Po Lu <luangruo@yahoo.com> 於 2022年4月15日 週五 上午12:49寫道:

> bg.jheng@gmail.com writes:
>
> > i also tried to comment out that you say this :
> >          else if (dpyinfo->xkb_desc->names->vmods[i] ==
> dpyinfo->Xatom_Hyper)
> >             dpyinfo->hyper_mod_mask |= vmodmask;
> >
> > after rebuild,
> > the capital letter can normally insert with shift now.
> > hope it useful.
>
> So something in your virtual modifier map is binding Shift to Hyper.
> That's a bug in your setup, not in Emacs.
>
> Thanks.
>

[-- Attachment #2: Type: text/html, Size: 1627 bytes --]

  reply	other threads:[~2022-04-15  3:37 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
     [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 [this message]
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='CAEFYKcOZFEjiYk_u=+gn+TW8T6XPSVOd5bRfettMMKrDYGx-qg@mail.gmail.com' \
    --to=bg.jheng@gmail.com \
    --cc=54889@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).