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 11:43:31 +1100 Message-ID: <20180207004331.q4cll6nyldse2bin@adversary.org> References: <20180206190518.f43jsoughhlsi22y@adversary.org> <20180206222722.5uf43fd56p44dk5z@adversary.org> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="regrbjghuatvbwuk" X-Trace: blaine.gmane.org 1517964131 23394 195.159.176.226 (7 Feb 2018 00:42:11 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 7 Feb 2018 00:42:11 +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 01:42:07 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 1ejDny-0004KR-Vx for ged-emacs-devel@m.gmane.org; Wed, 07 Feb 2018 01:41:43 +0100 Original-Received: from localhost ([::1]:55899 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejDq0-0000ne-EV for ged-emacs-devel@m.gmane.org; Tue, 06 Feb 2018 19:43:48 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:59301) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejDpt-0000ld-7y for emacs-devel@gnu.org; Tue, 06 Feb 2018 19:43:42 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ejDpo-0005mU-Ty for emacs-devel@gnu.org; Tue, 06 Feb 2018 19:43:41 -0500 Original-Received: from ec2-52-29-175-128.eu-central-1.compute.amazonaws.com ([52.29.175.128]:56128 helo=devious.adversary.org) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ejDpo-0005lR-LT for emacs-devel@gnu.org; Tue, 06 Feb 2018 19:43:36 -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:222606 Archived-At: --regrbjghuatvbwuk Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Tue, Feb 06, 2018 at 05:50:18PM -0500, Noam Postavsky wrote: > On Tue, Feb 6, 2018 at 5:27 PM, Ben McGinnes wrote: >=20 > > It will build and it will load ... it'll even load enough of my init > > to reach the theme at the end ... but I wouldn't exactly describe it > > as functional. What could be extracted from that is in the attached > > org-file. I was, however able to identify the bytecomp failure (which > > was also what wreaked havoc on the ERC+ZNC connection infinite loop. >=20 > You seem to be describing some different bugs from what is in the OP > of this thread. I think you should open new bugs in the tracker for > them (send email to bug-gnu-emacs@gnu.org). > (and please as much as possible, show how to replicate the bug > starting from emacs -Q) Sure, how many current OS X bugs have already been reported and which ones are they? I also want to be sure I'm not simply duplicating existing reported bugs. Oh, it might be worth mentioning that in spite of using Emacs for years, I didn't get around to subscribing to this list and the orgmode one until yesterday ... so I almost certainly won't have read back through the archives enough to know how long or short the osx bug list currently is. Nor do I know how pressing the release date for version 26 is, if it's even locked in at all. The build one I haven't properly replicated, the title one might be related to what I saw with ERC+ZNC since it pertains to the buffer-name, but it might be unrelated. The ns-modifier conflicts and all the related aspects of that, if there isn't a current bug then I can certainly provide all that and I may as well test my proposed solution while I'm at it. I do have a rather hectic couple of days or so, it might get pushed back to the weekend, but I'll see where I can squeeze it in. At worst, though, my bughunting efforts would only be delayed until early next week. I have compiled the another copy with the src/nsterm.* and lisp/cus-start.el copied from the working build from the 4th and though I've got to do a thorough audit, it's looking like much OS X pain lies pretty much exactly where I said. The lisp/cus-start.el file had the clues, but the majority of the butchery is in src/nsterm.m. I'll include diffs later, of course, but since this is likely frustrating others who may not want to wait for my schedule to lighten to get stuck into it; ad hoc info be here, proper bug report and recommendations (or outright fixes) to be advised. Regards, Ben --regrbjghuatvbwuk Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iHUEABEKAB0WIQSkiyjzmoPmPFW48w5Icjp1eQQexgUCWnpLpwAKCRBIcjp1eQQe xtB6AQDxS0Mrri2gRKJ9q9lQ8xTN/YrZqx0BblKX0J/wl8ywRwEArVCalRjYxDp4 zESfRkrOMgCoaC0jIPeNfm5+8avp1jM= =Fsl/ -----END PGP SIGNATURE----- --regrbjghuatvbwuk--