From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dan Nicolaescu Newsgroups: gmane.emacs.devel Subject: Re: merging Emacs.app Date: Wed, 05 Mar 2008 20:03:16 -0800 Message-ID: <200803060403.m2643HgL006230@sallyv1.ics.uci.edu> References: <18375.18663.981150.252393@kahikatea.snap.net.nz> <200803031629.m23GT4tH023615@sallyv1.ics.uci.edu> <200803050504.m2554JRn010804@sallyv1.ics.uci.edu> <200803051605.m25G5bfF012539@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1204776333 4323 80.91.229.12 (6 Mar 2008 04:05:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Thu, 6 Mar 2008 04:05:33 +0000 (UTC) Cc: Eli Zaretskii , Stefan Monnier , emacs-devel@gnu.org To: YAMAMOTO Mitsuharu Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Thu Mar 06 05:06:00 2008 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1JX7Ml-0005bw-IW for ged-emacs-devel@m.gmane.org; Thu, 06 Mar 2008 05:05:59 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JX7MD-0005Hr-IQ for ged-emacs-devel@m.gmane.org; Wed, 05 Mar 2008 23:05:25 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JX7M4-0005Dd-RW for emacs-devel@gnu.org; Wed, 05 Mar 2008 23:05:17 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JX7M3-0005A0-Cp for emacs-devel@gnu.org; Wed, 05 Mar 2008 23:05:16 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JX7M3-00059j-5y for emacs-devel@gnu.org; Wed, 05 Mar 2008 23:05:15 -0500 Original-Received: from sallyv1.ics.uci.edu ([128.195.1.109]) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_3DES_EDE_CBC_SHA1:24) (Exim 4.60) (envelope-from ) id 1JX7Lz-0002oL-As; Wed, 05 Mar 2008 23:05:11 -0500 X-ICS-MailScanner-Watermark: 1205380997.73875@2g0tSqdIstas10UVwUGkgA Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by sallyv1.ics.uci.edu (8.13.7+Sun/8.13.7) with ESMTP id m2643HgL006230; Wed, 5 Mar 2008 20:03:17 -0800 (PST) In-Reply-To: (YAMAMOTO Mitsuharu's message of "Thu, 06 Mar 2008 09:58:50 +0900") Original-Lines: 30 X-ICS-MailScanner: Found to be clean X-ICS-MailScanner-SpamCheck: not spam, SpamAssassin (score=-1.44, required 5, autolearn=disabled, ALL_TRUSTED -1.44) X-ICS-MailScanner-From: dann@mothra.ics.uci.edu X-detected-kernel: by monty-python.gnu.org: Solaris 10 (beta) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:91466 Archived-At: YAMAMOTO Mitsuharu writes: > >>>>> On Wed, 05 Mar 2008 08:05:36 -0800, Dan Nicolaescu said: > > >>> Hopefully the Mac OS X guys can get together and decide to support > >>> just one of the non-X11 ports... > >> > >> For Emacs 22, I'll maintain the Carbon port (and possibly the > >> Carbon+AppKit port) unless my development environment for older > >> versions of Mac OS gets broken. > >> > >> For Emacs 23, I don't have a plan to develop the Carbon port. The > >> Carbon+AppKit port may be for my personal use only (I already have > >> the Core Text font backend driver for Leopard, and I can ignore > >> multi-tty for my own use), unless the Cocoa/GNUstep port fails to > >> become good enough. > > > The question then is: would you be interested in using your > > expertise to help the Emacs.app port get merged into trunk, and get > > into a state that is at least as good as the Carbon port on > > emacs-22? > > One may think that the two ports mainly differs in the APIs they use, > but what's really different between them is their fundamental design > and policy. (Otherwise I wouldn't have tried to make another > Cocoa-based port.) Some of that experience should be portable though: ability to debug/diagnose problems, porting some of the relevant lisp code should all be useful.