From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Chong Yidong Newsgroups: gmane.emacs.devel Subject: Re: Interpretation of a space in regexp isearch? Date: Sun, 26 Aug 2012 12:06:49 +0800 Message-ID: <87r4qu8ffq.fsf@gnu.org> References: <502B2845.9070200@yandex.ru> <878vdgiv2d.fsf@gnu.org> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1345954022 5845 80.91.229.3 (26 Aug 2012 04:07:02 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Sun, 26 Aug 2012 04:07:02 +0000 (UTC) Cc: Bastien , emacs-devel@gnu.org, Dmitry Gutov To: Dani Moncayo Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sun Aug 26 06:07:02 2012 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1T5U7q-0001Bc-OL for ged-emacs-devel@m.gmane.org; Sun, 26 Aug 2012 06:07:02 +0200 Original-Received: from localhost ([::1]:35628 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T5U7o-0003Vg-Cm for ged-emacs-devel@m.gmane.org; Sun, 26 Aug 2012 00:07:00 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:39913) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T5U7m-0003Vb-1r for emacs-devel@gnu.org; Sun, 26 Aug 2012 00:06:58 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T5U7l-000758-84 for emacs-devel@gnu.org; Sun, 26 Aug 2012 00:06:57 -0400 Original-Received: from mail-pb0-f41.google.com ([209.85.160.41]:39261) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T5U7l-000754-26; Sun, 26 Aug 2012 00:06:57 -0400 Original-Received: by pbbro12 with SMTP id ro12so5774812pbb.0 for ; Sat, 25 Aug 2012 21:06:56 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=sender:from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-type; bh=maJYNnVxr+NYAYH5I3xBG1LK+ouVJwZAQd0TmigRCoo=; b=femQgK1XUcWSLVnvyvEg/82Y9GQZAPkBdJgUSVEHa3gmLS3syOthWk5yD/SOlwBlmW /KdVETyCeyDPRDZd5loq8uE11i5HPnFbe5hEwCr14slSJAT0SKszSy1oaGh9X0TitnKe 7Ez80EVcaQL3bm5lFW7rcKFk4Nvr5eLBL8n1okxZHHmGuWBZ4qV1jb2WpGw0llo+oJ8p dOGcsUoLejgKYPAf2z59qmM6CUyhbpN9lVlgE1rG6lrUC6gIDDQemQf3vZ3M2gbe+o/N wx2qus5UedBfF2lBAKVi6+VCWx5dkdt4ewtF6RRKR+TTajGM2olauRkQvHAJgl6tK9Oq YHXA== Original-Received: by 10.68.232.138 with SMTP id to10mr24316265pbc.77.1345954016232; Sat, 25 Aug 2012 21:06:56 -0700 (PDT) Original-Received: from ulysses (cm162.gamma80.maxonline.com.sg. [202.156.80.162]) by mx.google.com with ESMTPS id ka4sm11733915pbc.61.2012.08.25.21.06.51 (version=SSLv3 cipher=OTHER); Sat, 25 Aug 2012 21:06:55 -0700 (PDT) In-Reply-To: (Dani Moncayo's message of "Wed, 15 Aug 2012 11:11:47 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/24.2.50 (gnu/linux) X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 209.85.160.41 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:152839 Archived-At: Dani Moncayo writes: > IMO, that feature is what the user usually wants in an ordinary search > (regardless it's incremental or not; even if that search is part of a > ordinary replace command). > > On the other and, in a rexexp search (or regexp search&replace) I > think that the common case is the opposite: the user normally doesn't > want that feature. I committed a change to trunk to make non-regexp isearch match multiple spaces via search-spaces-regexp. As for regexp isearch, it seems disruptive to remove the feature now, since some some users might have grown to rely on it. So I left regexp isearch alone (i.e. it still does the multiple spaces matching). It is now possible to change the variable `search-whitespace-regexp' and give it a cons cell value, which specifies different behaviors for ordinary and regexp isearch.