From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: David Kastrup Newsgroups: gmane.emacs.devel Subject: Re: Malformed interactive spec in replace.el Date: 06 Jul 2004 12:31:31 +0200 Sender: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Message-ID: References: <20040706104047.587A.JMBARRANQUERO@wke.es> <20040706113527.5880.JMBARRANQUERO@wke.es> NNTP-Posting-Host: deer.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1089111303 19917 80.91.224.253 (6 Jul 2004 10:55:03 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 6 Jul 2004 10:55:03 +0000 (UTC) Cc: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Tue Jul 06 12:54:45 2004 Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by deer.gmane.org with esmtp (Exim 3.35 #1 (Debian)) id 1Bhnb3-0006qt-00 for ; Tue, 06 Jul 2004 12:54:45 +0200 Original-Received: from lists.gnu.org ([199.232.76.165]) by quimby.gnus.org with esmtp (Exim 3.35 #1 (Debian)) id 1Bhnb3-00082I-00 for ; Tue, 06 Jul 2004 12:54:45 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1Bhnd3-0003BD-LA for emacs-devel@quimby.gnus.org; Tue, 06 Jul 2004 06:56:49 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1Bhncf-00031Y-M1 for emacs-devel@gnu.org; Tue, 06 Jul 2004 06:56:25 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BhncY-0002yl-Id for emacs-devel@gnu.org; Tue, 06 Jul 2004 06:56:25 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BhncY-0002yC-HB for emacs-devel@gnu.org; Tue, 06 Jul 2004 06:56:18 -0400 Original-Received: from [199.232.76.164] (helo=fencepost.gnu.org) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BhnaQ-0001Dq-Cr for emacs-devel@gnu.org; Tue, 06 Jul 2004 06:54:06 -0400 Original-Received: from localhost ([127.0.0.1] helo=lola.goethe.zz) by fencepost.gnu.org with esmtp (Exim 4.34) id 1BhnEb-0006XZ-0X; Tue, 06 Jul 2004 06:31:33 -0400 Original-To: Juanma Barranquero In-Reply-To: <20040706113527.5880.JMBARRANQUERO@wke.es> Original-Lines: 53 User-Agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50 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: , Errors-To: emacs-devel-bounces+emacs-devel=quimby.gnus.org@gnu.org Xref: main.gmane.org gmane.emacs.devel:25478 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:25478 Juanma Barranquero writes: > On 06 Jul 2004 11:26:41 +0200 > David Kastrup wrote: > > > Our policy is feature freeze right now. "Policy" does not mean > > that exceptions are impossible, but then we should have some > > consensus about them. > > I know. > > > So you claim this is just Stefan's way of suggesting he thinks we > > should not concentrate on the release? > > No. What I "claim", if I do claim anything at all, is that in many > projects, the line between "bugfix" and "little feature" is vague It wasn't here as far as I was able to discern. > > I fail to see those changes as an "outcome" to an "experiment" trying > > to see whether we can "restrict outselves into working to get a > > release out". > > I'm not talking about those changes. I'm saying that, in the two or > three months we've been on pre-release mode, there's been quite a > few comments (mostly by RMS and you, IIRC) about the need to focus > on the release. That would suggest that people is (at least, on > your and RMS' eyes) not doing it. Doesn't that mean anything? You mean that when a team trainer or team mate is telling his players to try harder, the conclusion should be that they all stop trying because it appears it would take an effort to succeed? > But it's hard (if ever posible, or desirable) to push people one way > or other. Reminding people of things we all agreed on is not "pushing" in my book. I know that I am responsible for a lot of recent post-freeze movement of replace.el, and I start being sorry for it. Not because it was a bad idea to rather implement sensible additional semantics in the normal replacement commands than document the more awkward query-replace-regexp-eval, but because this has escalated from implementing \, in the interactive regexp reader to adding \? as a replacement for documenting the non-satisfactory \,(read-string) idea. If I had not already documented all of this in the manual, I'd be sorely tempted to rip everything except the basic \, out again since it would appear that I have been setting a bad example, even though I tried to reach consensus on the list about the immediate desirability of those changes before checking them in. -- David Kastrup, Kriemhildstr. 15, 44793 Bochum