unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Nick Helm <nick@tenpoint.co.nz>
To: Alan Third <alan@idiocy.org>
Cc: Tak Kunihiro <tkk@misasa.okayama-u.ac.jp>,
	"34984@debbugs.gnu.org" <34984@debbugs.gnu.org>
Subject: bug#34984: ns-right-command-modifier has influence to left
Date: Fri, 29 Mar 2019 08:35:28 +0000	[thread overview]
Message-ID: <m2o95uyt6a.fsf@tenpoint.co.nz> (raw)
In-Reply-To: <20190328215229.GB52808@breton.holly.idiocy.org> (Alan Third's message of "Thu, 28 Mar 2019 21:52:29 +0000")

Alan Third <alan@idiocy.org> writes:

> I can replicate this. The key is to swap command and option. I also
> see it using my swapped caps lock ‐> ctrl. It shows up as right
> control when I would expect it to be left.
>
> Unfortunately I’m not sure what we can do about it. 

This only seems to happen when the modifiers are swapped using System
Preferences. On my machine the problem goes away if I remap using
another method. 

Try putting the modifiers back to their defaults in System Preferemces
then running the following command (this swaps events left_alt and
left_gui, and right_alt and right_gui). Note that this won't survive
reboot.

$ hidutil property --set '{"UserKeyMapping":[{"HIDKeyboardModifierMappingSrc":0x7000000E2,"HIDKeyboardModifierMappingDst":0x7000000E3},{"HIDKeyboardModifierMappingSrc":0x7000000E3,"HIDKeyboardModifierMappingDst":0x7000000E2},{"HIDKeyboardModifierMappingSrc":0x7000000E6,"HIDKeyboardModifierMappingDst":0x7000000E7},{"HIDKeyboardModifierMappingSrc":0x7000000E7,"HIDKeyboardModifierMappingDst":0x7000000E6}]}'

You can probably do similar tricks with karabiner and other key
remappers. 

Nick

  reply	other threads:[~2019-03-29  8:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-25  0:57 bug#34984: ns-right-command-modifier has influence to left Tak Kunihiro
2019-03-25 21:41 ` Alan Third
2019-03-26  3:46   ` Tak Kunihiro
2019-03-28 21:52     ` Alan Third
2019-03-29  8:35       ` Nick Helm [this message]
2019-03-29  8:42       ` Tak Kunihiro

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=m2o95uyt6a.fsf@tenpoint.co.nz \
    --to=nick@tenpoint.co.nz \
    --cc=34984@debbugs.gnu.org \
    --cc=alan@idiocy.org \
    --cc=tkk@misasa.okayama-u.ac.jp \
    /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).