From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Ben McGinnes Newsgroups: gmane.emacs.devel Subject: Re: Emacs 26 MacOS bugs Date: Wed, 7 Feb 2018 13:13:01 +1100 Message-ID: <20180207021301.zpvpexdkewztqxo4@adversary.org> References: <20180206190518.f43jsoughhlsi22y@adversary.org> <20180206222722.5uf43fd56p44dk5z@adversary.org> <20180207004331.q4cll6nyldse2bin@adversary.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="ucl2rsfan2ezk5c7" X-Trace: blaine.gmane.org 1517969523 22471 195.159.176.226 (7 Feb 2018 02:12:03 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 7 Feb 2018 02:12:03 +0000 (UTC) User-Agent: NeoMutt/20171215 Cc: Emacs developers To: Noam Postavsky Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Feb 07 03:11:58 2018 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1ejFDH-0005Kp-7Q for ged-emacs-devel@m.gmane.org; Wed, 07 Feb 2018 03:11:55 +0100 Original-Received: from localhost ([::1]:35555 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejFFI-0007sY-IQ for ged-emacs-devel@m.gmane.org; Tue, 06 Feb 2018 21:14:00 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:50753) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejFET-0007pX-74 for emacs-devel@gnu.org; Tue, 06 Feb 2018 21:13:11 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ejFEQ-0001c9-0m for emacs-devel@gnu.org; Tue, 06 Feb 2018 21:13:09 -0500 Original-Received: from ec2-52-29-175-128.eu-central-1.compute.amazonaws.com ([52.29.175.128]:28628 helo=devious.adversary.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejFEP-0001bg-PE for emacs-devel@gnu.org; Tue, 06 Feb 2018 21:13:05 -0500 Content-Disposition: inline In-Reply-To: OpenPGP: "id=DB4724E6FA4286C92B4E55C4321E4E2373590E5D; url=http://www.adversary.org/ben-key.asc" X-detected-operating-system: by eggs.gnu.org: FreeBSD 9.x [fuzzy] X-Received-From: 52.29.175.128 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:222609 Archived-At: --ucl2rsfan2ezk5c7 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 06, 2018 at 08:33:31PM -0500, Noam Postavsky wrote: > On Tue, Feb 6, 2018 at 7:43 PM, Ben McGinnes wrote: >=20 > > Sure, how many current OS X bugs have already been reported and which > > ones are they? >=20 > Approximately these ones: > https://debbugs.gnu.org/cgi/pkgreport.cgi?include=3Dsubject%3Amacos;inclu= de=3Dsubject%3Aosx;package=3Demacs Cheers. >> I also want to be sure I'm not simply duplicating existing >> reported bugs. >=20 > Too late! You already reported it by sending it here. ;) Heh. Of course ... >> Nor do I know how pressing the release date for version 26 is, if >> it's even locked in at all. >=20 > AFAIK, there's no firm date, but emacs-26 is in feature freeze and > only taking very safe/urgent bug fixes. So it's possible these bugs > won't be fixed until after 26.1 I think I could make a very convincing argument regarding the modifier keys here being urgent. If it was only rendering the hyper key useless, then maybe you could argue it as not being urgent, but it's not merely that ... any attempt to assign the hyper function to any other key (e.g. right alt), just adds the hyper function instead of replacing the previous function with that. So if left alt is meta and you set right alt as hyper, it just becomes a combined hyper-meta. It's no longer possible to set the hyper key on its own. Which means the code commentary about changing the nil to none for all those ns modifier keys is, in fact, completely wrong. You *do* want nil there because if you're re-assigning the key to perform another task you actually do want to clear the original setting out of it. As for a stable fix, that's dead simple, roll back everything from the 2016 commit that was merged into master on the 5th and it's done. Anyway, I've got to wander off to one of those other pressing things and since it involves a wee small hospital visit, it takes priority. I'll try to take another look at this beast a little later. Regards, Ben --ucl2rsfan2ezk5c7 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABEKAB0WIQSkiyjzmoPmPFW48w5Icjp1eQQexgUCWnpgrQAKCRBIcjp1eQQe xi3dAQD3mutXBPSwP8QOzR9lxpabFLB8OIs0D82TP5cSkg8KvQD/cKX0ctDyt3vS K4KoecM3u34N/3lDK+64wSAoA4nPi40= =FKB6 -----END PGP SIGNATURE----- --ucl2rsfan2ezk5c7--