linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Michel Dänzer" <michel@daenzer.net>
To: John Horan <knasher@gmail.com>
Cc: Jiri Kosina <jkosina@suse.cz>, linux-input@vger.kernel.org
Subject: Re: [PATCH] unswap the grave and 102nd keys on Apple Alu ISO keyboard
Date: Tue, 12 May 2015 09:44:11 +0900	[thread overview]
Message-ID: <55514CDB.30904@daenzer.net> (raw)
In-Reply-To: <1431350579.5543.0@smtp.gmail.com>


[ Please keep the Cc list intact ]

On 11.05.2015 22:22, John Horan wrote:
>> What's the output of "xprop -root | grep XKB" for you?
> _XKB_RULES_NAMES(STRING) = "evdev", "pc104", "gb,us", "mac,",
> "compose:rctrl" 

I wonder if the reversed behaviour in X is due to the "mac," (variant?).
Which keyboard model did you choose in the system / X keyboard
configuration?


>> What's the behaviour for you in console?
> I'm using the American keymap in the console, so it prints backslash
> when I press the grave key on the internal keyboard, but the external
> keyboard is still swapped in relation to it (and actually outputs grave).  

So it sounds like the ISO quirk is working correctly for the external
keyboard, and there's actually a problem with the internal keyboard.


>> That assumes the ISO quirk is active for the internal keyboard as
>> well. Have you double-checked that?
> Yeah, and again just to be sure.  

How did you check?


-- 
Earthling Michel Dänzer               |               http://www.amd.com
Libre software enthusiast             |             Mesa and X developer
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2015-05-12  0:44 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01  9:17 [PATCH] unswap the grave and 102nd keys on Apple Alu ISO keyboard John Horan
2015-05-04  8:07 ` Jiri Kosina
2015-05-04  8:09   ` Jiri Kosina
2015-05-04  8:11     ` Jiri Kosina
2015-05-08  2:57       ` Michel Dänzer
     [not found]         ` <1431079408.1420.0@smtp.gmail.com>
2015-05-09  8:41           ` Michel Dänzer
     [not found]             ` <1431350579.5543.0@smtp.gmail.com>
2015-05-12  0:44               ` Michel Dänzer [this message]
     [not found]                 ` <1431424549.1489.0@smtp.gmail.com>
2015-05-12 10:06                   ` Michel Dänzer
2015-05-12 11:05                     ` John Horan
2015-05-13  1:16                       ` Michel Dänzer
2015-05-13 11:48                         ` John Horan
2015-05-13 11:48   ` John Horan

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

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

  git send-email \
    --in-reply-to=55514CDB.30904@daenzer.net \
    --to=michel@daenzer.net \
    --cc=jkosina@suse.cz \
    --cc=knasher@gmail.com \
    --cc=linux-input@vger.kernel.org \
    /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.
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 NNTP newsgroup(s).