Date: Mon, 28 Dec 2020 19:12:48 +0000 From: bugzilla-noreply@freebsd.org To: x11@FreeBSD.org Subject: [Bug 252235] x11/xorg: MacBook Pro 8,3 faulty key mapping Message-ID: <bug-252235-7141-ZwyE6lMyYl@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-252235-7141@https.bugs.freebsd.org/bugzilla/> References: <bug-252235-7141@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D252235 --- Comment #5 from Jason W. Bacon <jwb@freebsd.org> --- Great, thanks for the additional info. I'd love to hear from anyone using a newer MacBook about the keymap issue, given that my MacBooks range from very old to fossilized. The problem in symbols/us is here: xkb_symbols "mac" { include "us(basic)" name[Group1]=3D "English (Macintosh)"; key.type[group1]=3D"FOUR_LEVEL"; // Slightly improvised from http://homepage.mac.com/thgewecke/kblayout.= jpg key <LSGT> { [ section, plusminus, section, plusminus ]= }; key <TLDE> { [ grave, asciitilde, dead_grave, dead_horn ]= }; key <AE01> { [ 1, exclam, exclamdown, U2044 ]= }; Switching LSGT and TLDE fixes the problem on my MacBook Pro 8,3 (from 2009), but I wonder if this would actually break newer Macs. If that's the case, = all I can think of is defining a separate variant. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-252235-7141-ZwyE6lMyYl>