From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Bidi support Date: Fri, 21 Aug 2009 23:44:11 +0300 Message-ID: <833a7khp7o.fsf@gnu.org> References: <87praszybe.fsf@stupidchicken.com> <838whgik6y.fsf@gnu.org> <8363cjipz6.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: lo.gmane.org X-Trace: ger.gmane.org 1250887589 15118 80.91.229.12 (21 Aug 2009 20:46:29 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 21 Aug 2009 20:46:29 +0000 (UTC) Cc: cyd@stupidchicken.com, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Aug 21 22:46:21 2009 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 1Meb08-00039b-LB for ged-emacs-devel@m.gmane.org; Fri, 21 Aug 2009 22:46:21 +0200 Original-Received: from localhost ([127.0.0.1]:48431 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Meb07-0000ps-Vc for ged-emacs-devel@m.gmane.org; Fri, 21 Aug 2009 16:46:20 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Meb02-0000pm-Pz for emacs-devel@gnu.org; Fri, 21 Aug 2009 16:46:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Meb01-0000pC-O8 for emacs-devel@gnu.org; Fri, 21 Aug 2009 16:46:14 -0400 Original-Received: from [199.232.76.173] (port=38761 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Meb01-0000p2-K8 for emacs-devel@gnu.org; Fri, 21 Aug 2009 16:46:13 -0400 Original-Received: from mtaout6.012.net.il ([84.95.2.16]:38819) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Meb01-0006tP-46 for emacs-devel@gnu.org; Fri, 21 Aug 2009 16:46:13 -0400 Original-Received: from conversion-daemon.i-mtaout6.012.net.il by i-mtaout6.012.net.il (HyperSendmail v2007.08) id <0KOQ00E00UKZSR00@i-mtaout6.012.net.il> for emacs-devel@gnu.org; Fri, 21 Aug 2009 23:46:11 +0300 (IDT) Original-Received: from HOME-C4E4A596F7 ([84.228.180.85]) by i-mtaout6.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0KOQ00HJ4V0WNC70@i-mtaout6.012.net.il>; Fri, 21 Aug 2009 23:46:09 +0300 (IDT) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by monty-python.gnu.org: Solaris 10 (1203?) 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:114496 Archived-At: > From: Stefan Monnier > Cc: cyd@stupidchicken.com, emacs-devel@gnu.org > Date: Fri, 21 Aug 2009 14:59:24 -0400 > > Has this branch been kept up-to-date w.r.t the trunk? No. > I'd guess not. In that case, someone should do it. I already did. I have a source tree where the bidi code is merged with the current trunk, and I merge them as needed all the time. That's where I do all the development beyond what's on the bidi branch (which is dead, as far as I'm concerned). I can keep it that way forever, but I'd prefer to have it in the repository soon, because others might wish to work on it. > Agreed. The more I think about it, the more I think we need to open > a new branch for "what will become emacs-24". Kind of like what we did > with the emacs-unicode branch. I think bidi should be one of the first > features to install on that branch. Why not the other way around: make a branch for Emacs 23.x, and leave Emacs 24 on the trunk? I think Yidong suggested that, and I think it's a better idea. We never left the mainline of our development on a branch before. > I think it will stay unstable for too long, so it's not good enough for > the current trunk (which I'd like to keep for shorter-term changes). I guess that's a NO, but please note that this code, however unstable, is never executed unless the user flips a variable. So I don't see how it can destabilize the default configuration by being dead ballast.