From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Paul Michael Reilly Newsgroups: gmane.emacs.devel Subject: Re: Emacs on OS X development Date: Thu, 12 Jul 2012 20:57:08 -0400 Message-ID: References: NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=f46d042e00f94408c304c4ab8f66 X-Trace: dough.gmane.org 1342141039 2160 80.91.229.3 (13 Jul 2012 00:57:19 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Fri, 13 Jul 2012 00:57:19 +0000 (UTC) To: gmane.emacs.devel@vulcan.local, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Jul 13 02:57:19 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1SpUC4-0004pt-LI for ged-emacs-devel@m.gmane.org; Fri, 13 Jul 2012 02:57:16 +0200 Original-Received: from localhost ([::1]:44926 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SpUC3-0005wJ-Pb for ged-emacs-devel@m.gmane.org; Thu, 12 Jul 2012 20:57:15 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:48693) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SpUC0-0005w0-PN for emacs-devel@gnu.org; Thu, 12 Jul 2012 20:57:13 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SpUBz-0004zg-3A for emacs-devel@gnu.org; Thu, 12 Jul 2012 20:57:12 -0400 Original-Received: from mail-yx0-f169.google.com ([209.85.213.169]:58814) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SpUBy-0004zZ-Tm for emacs-devel@gnu.org; Thu, 12 Jul 2012 20:57:11 -0400 Original-Received: by yenr5 with SMTP id r5so3561454yen.0 for ; Thu, 12 Jul 2012 17:57:09 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:x-gm-message-state; bh=ROPiKD+CKzWOAl1nsv4CUVVxBhhvGdVkwxcQibDwivk=; b=A5CCiTm/AXr+biVc9mVuEoft4/IjvMjrWSd5DlZP/gxzlc+A2QNtYDMKC0Dxv1rv+L cs72Ynhb0+HiFKWoKriQ42nEAc7gmVmYGLbQjtngktsp3WIUpJGgqWJqDDBoA4+iHCPP nlLarP6jbtyVj+KItzkQf7DSQ43Wb4f+Npapt4ITEXs+RT37L2iji3SU02W2WAOI8Vv/ uDh1nxkEZKfDnDZ65UYFEv/7hFnvXDDTTnYJ4NzU/87WzJN7oN6t/fYxG02yGwge3ioI hi1dPkaZIwrokXolxwPCUZLHcphKIa8ZL38b/FW+CDIw+CUC9vdzp/DUHN/5zBJtkYJx NByw== Original-Received: by 10.66.78.10 with SMTP id x10mr593556paw.80.1342141028894; Thu, 12 Jul 2012 17:57:08 -0700 (PDT) Original-Received: by 10.142.163.4 with HTTP; Thu, 12 Jul 2012 17:57:08 -0700 (PDT) In-Reply-To: X-Gm-Message-State: ALoCoQkFo7OkrWWL5/b+eLW7KeWpQcMbwdnZJYME0CurXmg48A7lYlKf50MnYmEf+ReQyFS75+AY X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.213.169 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 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-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:151574 Archived-At: --f46d042e00f94408c304c4ab8f66 Content-Type: text/plain; charset=ISO-8859-1 On Thu, Jul 12, 2012 at 8:23 PM, John Wiegley wrote: > >>>>> Stefan Monnier writes: > > >> back to nsport. The difference is that noticeable. We have been hoping > the > >> nsport get better. It seems 3 years have passed. > > > Waiting ain't gonna fix it, indeed. > > Stefan, I want to bring up again the possibility of switching the Mac port > over to Yamamoto's code. Is there any reason not to? I just tried the ns > port again, and within minutes couldn't tolerate it: > > 1. The colors are washed out, compared to Mac-Port. > > 2. The leading on Courier is all wrong. Example: The pixels from the top > of > capital letters run into the mode-line. I need to set line-spacing to > 3 > just to make text look decent. > > 3. If I switch to *scratch* and turn on flyspell, I can out-type Emacs > very > easily, the lag is that bad. > > Why are we sticking with the ns port again, when Yamamoto has been so > active > in keeping the Mac-Port patch maintained? > This sounds strange to me. I've been compiling the devel source on my Mac Mini and thinking that it was as good as it gets. So I have two questions: 1) Can someone summarize the pros and cons of each approach to give those of us who care a chance to weigh in, and 2) Are there any prebuilt binaries for the alternative Mac approach that I can try out? fwiw, my experience with using MacPorts and other Mac package suppliers has been less than joyful. To be brutally honest I found it to be a royal pain in the butt. But if the benefit of overcoming the pain yields a substantial Emacs reward, then I will gladly give it another shot. -pmr --f46d042e00f94408c304c4ab8f66 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
On Thu, Jul 12, 2012 at 8:23 PM, John Wiegley <johnw@newartisans.com> wrote:
>>>>> Stefan Monnier= <monnier@iro.umontreal.ca> writes:

>> back to nsport. The difference is that noticeable. We have been ho= ping the
>> nsport get better. It seems 3 years have passed.

> Waiting ain't gonna fix it, indeed.

Stefan, I want to bring up again the possibility of switching t= he Mac port
over to Yamamoto's code. =A0Is there any reason not to? =A0I just tried= the ns
port again, and within minutes couldn't tolerate it:

=A01. The colors are washed out, compared to Mac-Port.

=A02. The leading on Courier is all wrong. =A0Example: The pixels from the = top of
=A0 =A0 capital letters run into the mode-line. =A0I need to set line-spaci= ng to 3
=A0 =A0 just to make text look decent.

=A03. If I switch to *scratch* and turn on flyspell, I can out-type Emacs v= ery
=A0 =A0 easily, the lag is that bad.

Why are we sticking with the ns port again, when Yamamoto has been so activ= e
in keeping the Mac-Port patch maintained?
This sounds strange to me. =A0I've been compiling the devel source on= my Mac Mini and thinking that it was as good as it gets. =A0 So I have two= questions:

1) Can someone summarize the pros and cons of each appr= oach to give those of us who care a chance to weigh in, and

<= /div>
2) Are there any prebuilt binaries for the alternative Mac approa= ch that I can try out?

fwiw, my experience with using MacPorts and other Mac p= ackage suppliers has been less than joyful. =A0To be brutally honest I foun= d it to be a royal pain in the butt. =A0But if the benefit of overcoming th= e pain yields a substantial Emacs reward, then I will gladly give it anothe= r shot.

-pmr

--f46d042e00f94408c304c4ab8f66--