From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: YAMAMOTO Mitsuharu Newsgroups: gmane.emacs.devel Subject: Re: Next release Date: Sun, 04 May 2008 10:57:17 +0900 Organization: Faculty of Science, Chiba University Message-ID: References: <18457.37369.262079.668907@kahikatea.snap.net.nz> <5jr6clncn8.fsf@fencepost.gnu.org> <87od7p22dw.fsf@stupidchicken.com> <200805021331.m42DVYVw016584@sallyv1.ics.uci.edu> <200805021610.m42GAhkE001271@sallyv1.ics.uci.edu> <200805040056.m440u3eS022727@sallyv1.ics.uci.edu> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 (generated by SEMI 1.14.6 - "Maruoka") Content-Type: text/plain; charset=US-ASCII X-Trace: ger.gmane.org 1209866260 4531 80.91.229.12 (4 May 2008 01:57:40 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 4 May 2008 01:57:40 +0000 (UTC) Cc: Glenn Morris , Chong Yidong , Dan Nicolaescu , Nick Roberts , emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun May 04 03:58:13 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 1JsTUT-0008Vm-KC for ged-emacs-devel@m.gmane.org; Sun, 04 May 2008 03:58:13 +0200 Original-Received: from localhost ([127.0.0.1]:58029 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsTTm-0001Nj-7m for ged-emacs-devel@m.gmane.org; Sat, 03 May 2008 21:57:30 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1JsTTh-0001NU-Hy for emacs-devel@gnu.org; Sat, 03 May 2008 21:57:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1JsTTf-0001NI-2r for emacs-devel@gnu.org; Sat, 03 May 2008 21:57:23 -0400 Original-Received: from [199.232.76.173] (port=52954 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1JsTTe-0001NF-Ma for emacs-devel@gnu.org; Sat, 03 May 2008 21:57:22 -0400 Original-Received: from mathmail.math.s.chiba-u.ac.jp ([133.82.132.2]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1JsTTa-0005E5-QM; Sat, 03 May 2008 21:57:19 -0400 Original-Received: from church.math.s.chiba-u.ac.jp (church [133.82.132.36]) by mathmail.math.s.chiba-u.ac.jp (Postfix) with ESMTP id C6EC72C40; Sun, 4 May 2008 10:57:17 +0900 (JST) In-Reply-To: User-Agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.8 (=?ISO-8859-4?Q?Shij=F2?=) APEL/10.6 Emacs/23.0.50 (sparc-sun-solaris2.8) MULE/5.0 (SAKAKI) X-detected-kernel: by monty-python.gnu.org: NetBSD 3.0 (DF) 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:96407 Archived-At: >>>>> On Sat, 03 May 2008 21:40:38 -0400, Stefan Monnier said: > We're still waiting for someone to actually finish the merge w.r.t > the Carbon port. This can only be done by someone who understand > enough of the Carbon port. You seem like our best hope here. As I said in http://lists.gnu.org/archive/html/emacs-devel/2008-03/msg00419.html, I don't have a plan to develop the Carbon (not Carbon+AppKit) port of Emacs 23. > I do not know why you seem to be so offended by the multi-tty code. > Maybe if you explained it, we could work it through. Its being > non-working and without anybody willing to fix it is basically the > main reason why we started to look into the Emacs.app code. It is a > pity to throw away this code. The breakage of the Carbon port is definitely NOT a reason. Well, one of the reasons would be that I found some changes that are totally unrelated to multi-tty. Another reason is no clear explanation given about preloading term/*-win. >> Just like you literally replaced `next-line' with `forward-line' to >> remove byte-compiler warnings without considering their meanings. > Everybody makes mistakes. Now, can we go back to improving Emacs > instead of bitching at each other? Yes, of course. But some level of carefulness would be expected for those who have a write access, I think. YAMAMOTO Mitsuharu mituharu@math.s.chiba-u.ac.jp