From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dmitry Gutov Newsgroups: gmane.emacs.devel Subject: Re: Interpretation of a space in regexp isearch? Date: Wed, 15 Aug 2012 08:40:37 +0400 Message-ID: <502B2845.9070200@yandex.ru> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Trace: dough.gmane.org 1345005653 11152 80.91.229.3 (15 Aug 2012 04:40:53 GMT) X-Complaints-To: usenet@dough.gmane.org NNTP-Posting-Date: Wed, 15 Aug 2012 04:40:53 +0000 (UTC) Cc: bzg@gnu.org, emacs-devel@gnu.org To: cyd@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Aug 15 06:40:48 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 1T1VPS-0005tp-V0 for ged-emacs-devel@m.gmane.org; Wed, 15 Aug 2012 06:40:47 +0200 Original-Received: from localhost ([::1]:60563 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1VPR-0000ny-Fr for ged-emacs-devel@m.gmane.org; Wed, 15 Aug 2012 00:40:45 -0400 Original-Received: from eggs.gnu.org ([208.118.235.92]:39580) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1VPN-0000nd-TV for emacs-devel@gnu.org; Wed, 15 Aug 2012 00:40:42 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1T1VPM-0001kX-Vu for emacs-devel@gnu.org; Wed, 15 Aug 2012 00:40:41 -0400 Original-Received: from forward17.mail.yandex.net ([95.108.253.142]:33413) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1T1VPI-0001jo-Kp; Wed, 15 Aug 2012 00:40:36 -0400 Original-Received: from smtp17.mail.yandex.net (smtp17.mail.yandex.net [95.108.252.17]) by forward17.mail.yandex.net (Yandex) with ESMTP id 9C88D1061E9B; Wed, 15 Aug 2012 08:40:34 +0400 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1345005634; bh=6I5kARvM3tlOTu5zcjeHHpP2ojirQYrXYk/B7UnskPY=; h=Message-ID:Date:From:MIME-Version:To:CC:Subject:Content-Type: Content-Transfer-Encoding; b=Z0YcIG7Tsr400zsZSVSLYCFmI7HZ/lL7ywlAz0wGKtF1W5uipCaW0gtd92g9t0AfG Q6Cn4oHNhRAZ0SUVXZgEClZzaprazwiQQNK0gHL2EbHUIVpeErEgNsdG4JYNtCB+jH Xto4BMNQ+nxx5hWVCrhtL6VfrILCi4EiCTqkF6dA= Original-Received: from smtp17.mail.yandex.net (localhost [127.0.0.1]) by smtp17.mail.yandex.net (Yandex) with ESMTP id 6920F190086D; Wed, 15 Aug 2012 08:40:34 +0400 (MSK) Original-Received: from 5x164x77x95.dynamic.spb.ertelecom.ru (5x164x77x95.dynamic.spb.ertelecom.ru [5.164.77.95]) by smtp17.mail.yandex.net (nwsmtp/Yandex) with ESMTP id eXI04ELP-eXIC14tG; Wed, 15 Aug 2012 08:40:34 +0400 X-Yandex-Rcpt-Suid: cyd@gnu.org X-Yandex-Rcpt-Suid: bzg@gnu.org X-Yandex-Rcpt-Suid: emacs-devel@gnu.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yandex.ru; s=mail; t=1345005634; bh=6I5kARvM3tlOTu5zcjeHHpP2ojirQYrXYk/B7UnskPY=; h=Message-ID:Date:From:User-Agent:MIME-Version:To:CC:Subject: Content-Type:Content-Transfer-Encoding; b=DsdYzUR9S/EHtTBGBRSy0wdrOkVhs0G9JqHmQ8QPN6XYUkz/cEAPklXD/U9dQ9D3Y Okd5vsGFHNmheNU4F1+Im9cs30JgqmrhTHBx3P4wOYV3kUNjEb+52fcj7ekygOY/8T L8ffaAHug5wVYIJX/k/NQzdOkypEMBc2Qp5xXc20= User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:14.0) Gecko/20120713 Thunderbird/14.0 X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 95.108.253.142 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:152537 Archived-At: Chong Yidong writes: > Bastien writes: > >> Davis Herring writes: >> >>> It's a feature, but I don't remember how to change it at the moment. >>> `search-spaces-regexp' is almost it. >> >> Yep -- it's =CC=80search-whitespace-regexp'. > > FWIW, I've long been of the opinion that this feature is exactly > backward. The `search-whitespace-regexp' whitespace matching feature > should apply to ordinary incremental search, and it should *not* apply > to regexp incremental search. I think that would make more sense, too.