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: Multi-tty design (Re: Reordering etc/NEWS) Date: Mon, 14 May 2007 14:02:47 -0700 Message-ID: <200705142102.l4EL2pHK013655@oogie-boogie.ics.uci.edu> References: <851whkrioc.fsf@lola.goethe.zz> <85hcqg4qxs.fsf@lola.goethe.zz> <85d5144p78.fsf@lola.goethe.zz> <200705131822.l4DIMtXt019128@oogie-boogie.ics.uci.edu> <85abw8o51q.fsf@lola.goethe.zz> <464835DE.3020007@lorentey.hu> <86y7jrr8rx.fsf@lola.quinscape.zz> <86lkfrr3s6.fsf@lola.quinscape.zz> <86d513r2i1.fsf@lola.quinscape.zz> <861whjr097.fsf@lola.quinscape.zz> <200705141648.l4EGmmvW007675@oogie-boogie.ics.uci.edu> <85bqgngvos.fsf@lola.goethe.zz> <200705141819.l4EIJLPr009832@oogie-boogie.ics.uci.edu> <85ps53fcm0.fsf@lola.goethe.zz> <200705142004.l4EK4DHg012188@oogie-boogie.ics.uci.edu> <85lkfrf91x.fsf@lola.goethe.zz> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1179176769 11646 80.91.229.12 (14 May 2007 21:06:09 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Mon, 14 May 2007 21:06:09 +0000 (UTC) Cc: Andreas Schwab , Karoly Lorentey , joakim@verona.se, emacs-devel@gnu.org To: David Kastrup Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon May 14 23:06:07 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 1Hnhjx-0003iF-86 for ged-emacs-devel@m.gmane.org; Mon, 14 May 2007 23:05:57 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Hnhrk-0005al-EO for ged-emacs-devel@m.gmane.org; Mon, 14 May 2007 17:14:00 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1HnhrM-0005DI-RA for emacs-devel@gnu.org; Mon, 14 May 2007 17:13:36 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1HnhrM-0005Cy-68 for emacs-devel@gnu.org; Mon, 14 May 2007 17:13:36 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1HnhrL-0005Cu-Vb for emacs-devel@gnu.org; Mon, 14 May 2007 17:13:36 -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 1HnhjW-0007bD-OH; Mon, 14 May 2007 17:05:31 -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 l4EL2pHK013655; Mon, 14 May 2007 14:02:51 -0700 (PDT) In-Reply-To: <85lkfrf91x.fsf@lola.goethe.zz> (David Kastrup's message of "Mon\, 14 May 2007 22\:24\:10 +0200") Original-Lines: 40 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:71068 Archived-At: David Kastrup writes: > Dan Nicolaescu writes: > > > David Kastrup writes: > > > > So reverting the change is not the right solution. Personally, > > > I think the arguments of getenv and setenv are completely messed > > > up. > > [You deleted the whole discussion and proposal for making a more > stable solution] Yes, intentionally as it is irrelevant here. Before your change people were able to test the multi-tty functionality, after it they are not. Nobody claimed the code was bug free, but it did do what was advertised to do. This shows a total lack of respect for all the hard work Karoly's put in for a few years. > > It is at this point. You changed the code from working into > > non-working, > > Wrong. I changed code from _not_ working as advertised to _working_ > as advertised. Which means that a bug in a _caller_ now gets exposed. > You think that the right solution for the problem is hiding the bug in > the caller again, making the function do something different from what > the documentation claims it does. You left the tree in an broken state, you didn't even debug the problem that you caused. THAT is wrong. > I'll try to see whether I can find the problematic caller. But I > certainly hope that this "paper over it and hope nobody notices it" > stance does not pervade multi-tty, and that the _bug_ which I fixed > was not intentional but an oversight. This is totally uncalled for. I have already given you a trivial way to find the caller.