From: John Horan <knasher@gmail.com>
To: "Michel Dänzer" <michel@daenzer.net>
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: Wed, 13 May 2015 12:48:11 +0100 [thread overview]
Message-ID: <1431517691.1582.0@smtp.gmail.com> (raw)
In-Reply-To: <5552A5F4.2020501@daenzer.net>
> It makes some sense, but OTOH it sounded like in console it's actually
> the external keyboard which is working correctly for you.
I wouldn't say that. The external keyboard was wrong according to the
keymap applied to it.
> Also, my Apple keyboard isn't connected to an Apple machine but to an
> HP
> notebook. How do you suggest such a combination should be configured
> without the ISO quirk?
I'd imagine your HP notebook has an American keyboard. In your case my
personal preference would be that the keymaps would match and when I
press the button next to 1, tilda is printed regardless of the keyboard
I'm using. If you prefer to use the keymap which matches the symbols
printed on the keyboard, then I believe you can specify a per keyboard
keymap using udev and setxkbmap. Though to be honest I think this
would be a clunky solution, as setxkbmap seems to apply to X alone; I
don't know if there is a better solution.
> Finally, I still find it hard to believe that this issue would only
> affect this particular Apple ISO keyboard model.
I suspect it doesn't. In particular when googling for this I found a
lot of people disabling the iso_layout quirk for the MacbookAir2013
models[1][2]. The ISO keyboard on my laptop definetly requires it, but
I suspect the quirk has been applied more broadly that it should have
been.
-John
[1]http://atodorov.org/blog/2015/04/30/fixing-tilde-and-function-keys-mapping-for-macbook-air-on-linux/
[2]https://bugzilla.redhat.com/show_bug.cgi?id=1025041#c2
next prev parent reply other threads:[~2015-05-13 11:48 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
[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 [this message]
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=1431517691.1582.0@smtp.gmail.com \
--to=knasher@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=michel@daenzer.net \
/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).