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: Post-22.1 development? Date: Mon, 11 Jun 2007 10:02:26 -0700 Message-ID: <200706111702.l5BH2Q2w000121@oogie-boogie.ics.uci.edu> References: <878xb05ras.fsf@stupidchicken.com> <200706101559.l5AFxBFb006829@oogie-boogie.ics.uci.edu> <86fy4yg62v.fsf@lola.quinscape.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1181581500 5293 80.91.229.12 (11 Jun 2007 17:05:00 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 11 Jun 2007 17:05:00 +0000 (UTC) To: rms@gnu.org, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Jun 11 19:04:59 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 1HxnK4-0003rq-Sp for ged-emacs-devel@m.gmane.org; Mon, 11 Jun 2007 19:04:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HxnK4-0004Is-4b for ged-emacs-devel@m.gmane.org; Mon, 11 Jun 2007 13:04:56 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HxnK0-0004Gv-RZ for emacs-devel@gnu.org; Mon, 11 Jun 2007 13:04:52 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HxnJz-0004Dv-Db for emacs-devel@gnu.org; Mon, 11 Jun 2007 13:04:51 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HxnJz-0004Dg-5e for emacs-devel@gnu.org; Mon, 11 Jun 2007 13:04:51 -0400 Original-Received: from oogie-boogie.ics.uci.edu ([128.195.1.41]) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1HxnJw-00086j-22; Mon, 11 Jun 2007 13:04:48 -0400 Original-Received: from mothra.ics.uci.edu (mothra.ics.uci.edu [128.195.6.93]) by oogie-boogie.ics.uci.edu (8.13.6/8.13.6) with ESMTP id l5BH2Q2w000121; Mon, 11 Jun 2007 10:02:26 -0700 (PDT) In-Reply-To: <86fy4yg62v.fsf@lola.quinscape.zz> (David Kastrup's message of "Mon\, 11 Jun 2007 12\:04\:40 +0200") Original-Lines: 48 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: Solaris 9 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:72627 Archived-At: David Kastrup writes: > Richard Stallman writes: > > > How about merging the multi-tty branch? The changes on that branch are > > much more localized, so porting fixes from the trunk to the EMACS_22 > > branch should not be a big issue. > > > > Does anyone see a problem with this idea? > > Well, the setenv/process-environment thing I wanted to have a look at: > in the current state, it will require quite a few changes in existing > packages (including packages not distributed as part of Emacs), and I > think that the approach which I sketched out would pretty much > eliminate that problem. Let me reiterate Karoly's (the multi-tty author) opinion on this, which I also second as a contributor to that branch and as a (almost exclusive) user for about 2 years: the environment variables thing is a peripheral issue, and a rather obscure one. Changing this requires about 50-100 lines of code (including comments) and it can be done without major impact on the rest of the multi-tty functionality (it has happened a few times on the multi-tty branch already). Karoly does not think there's a problem with the current implementation (and I second that too), but he would have no objection if David was to replace the current implementation. > Merging multi-tty to the trunk now could mean that some people start > patching up other packages inside or outside of Emacs to work with the > current environment variable settings, while others will change the > mechanisms eventually. The changes in question for external packages probably amount to 1-2 lines of code. Plus I don't think we should be concerned about external packages at this point. For the code in Emacs, if the implementation changes I volunteer to go over and fix any issues. I guesstimate this to be less than 10 minutes of work. So in conclusion _my_ (quite informed) opinion is that this issue should not stop a merge. Please let's move forward unless there are more serious issues that need consideration.