From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Ted Zlatanov Newsgroups: gmane.emacs.devel Subject: Re: 23.0.50; MacOS X 10.4: very slow visuals, multi-tty patch suspected Date: Wed, 26 Sep 2007 06:52:36 -0500 Organization: =?utf-8?B?0KLQtdC+0LTQvtGAINCX0LvQsNGC0LDQvdC+0LI=?= @ Cienfuegos Message-ID: References: <200709061414.l86EEwQE013656@oogie-boogie.ics.uci.edu> <200709061610.l86GAA2D017210@oogie-boogie.ics.uci.edu> <200709061715.l86HFHXx020325@oogie-boogie.ics.uci.edu> <200709061843.l86IhFrJ023998@oogie-boogie.ics.uci.edu> <200709062016.l86KGW4i027628@oogie-boogie.ics.uci.edu> <46F92348.2050203@gnu.org> <46F97307.6040904@gnu.org> <200709260544.l8Q5iVaB015270@oogie-boogie.ics.uci.edu> <46FA0BC1.9020403@gnu.org> <46FA0DCA.2010107@gnu.org> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1190808220 11637 80.91.229.12 (26 Sep 2007 12:03:40 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Wed, 26 Sep 2007 12:03:40 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 26 14:03:34 2007 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 1IaVc5-0007FJ-VB for ged-emacs-devel@m.gmane.org; Wed, 26 Sep 2007 14:03:34 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IaVc3-0006jQ-1a for ged-emacs-devel@m.gmane.org; Wed, 26 Sep 2007 08:03:31 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1IaVbz-0006j6-NP for emacs-devel@gnu.org; Wed, 26 Sep 2007 08:03:27 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1IaVbv-0006iX-8o for emacs-devel@gnu.org; Wed, 26 Sep 2007 08:03:27 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1IaVbv-0006iU-5j for emacs-devel@gnu.org; Wed, 26 Sep 2007 08:03:23 -0400 Original-Received: from main.gmane.org ([80.91.229.2] helo=ciao.gmane.org) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1IaVbu-0003pa-A1 for emacs-devel@gnu.org; Wed, 26 Sep 2007 08:03:22 -0400 Original-Received: from list by ciao.gmane.org with local (Exim 4.43) id 1IaVav-0006BS-HW for emacs-devel@gnu.org; Wed, 26 Sep 2007 12:02:21 +0000 Original-Received: from c-24-14-57-89.hsd1.il.comcast.net ([24.14.57.89]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 Sep 2007 12:02:21 +0000 Original-Received: from tzz by c-24-14-57-89.hsd1.il.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Wed, 26 Sep 2007 12:02:21 +0000 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 13 Original-X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: c-24-14-57-89.hsd1.il.comcast.net X-Face: bd.DQ~'29fIs`T_%O%C\g%6jW)yi[zuz6; d4V0`@y-~$#3P_Ng{@m+e4o<4P'#(_GJQ%TT= D}[Ep*b!\e,fBZ'j_+#"Ps?s2!4H2-Y"sx" User-Agent: Gnus/5.110007 (No Gnus v0.7) Emacs/22.1.50 (darwin) Cancel-Lock: sha1:MuDCOiBx29eyHyMjAqVz01rpdoY= X-Detected-Kernel: Linux 2.6, seldom 2.4 (older, 4) 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:79900 Archived-At: On Wed, 26 Sep 2007 11:19:47 +0200 Eli Zaretskii wrote: EZ> Personally, I find it disturbing that many Free Software projects EZ> consider removing bit-rotting builds too easily. I like the fact that EZ> Emacs is a notable exception from this rule. So I don't think we EZ> should remove the Mac build in question so quickly and so easily. I did not suggest removal, only disabling or documenting the Carbon port. Documenting would at least tell users that it's unusable interactively and that help is needed. I also did not suggest it should be quick or easy :) Ted