From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: "Ken Manheimer" Newsgroups: gmane.emacs.help Subject: emacs 22 - regular-expression isearch on spaces extremely lenient Date: Fri, 28 Apr 2006 16:56:45 -0400 Message-ID: <2cd46e7f0604281356i582388e2kef07922b6b6a9a3a@mail.gmail.com> References: <2cd46e7f0604281353l38f7672gd3cfe0c64fdf0cb4@mail.gmail.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: sea.gmane.org 1146290570 7379 80.91.229.2 (29 Apr 2006 06:02:50 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Sat, 29 Apr 2006 06:02:50 +0000 (UTC) Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Apr 29 08:02:47 2006 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1FZiXW-00034u-6n for geh-help-gnu-emacs@m.gmane.org; Sat, 29 Apr 2006 08:02:47 +0200 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FZiXV-0007UV-Qz for geh-help-gnu-emacs@m.gmane.org; Sat, 29 Apr 2006 02:02:45 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1FZa1A-0003wc-LW for help-gnu-emacs@gnu.org; Fri, 28 Apr 2006 16:56:48 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1FZa19-0003vo-86 for help-gnu-emacs@gnu.org; Fri, 28 Apr 2006 16:56:48 -0400 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1FZa18-0003vc-T0 for help-gnu-emacs@gnu.org; Fri, 28 Apr 2006 16:56:46 -0400 Original-Received: from [64.233.182.186] (helo=nproxy.gmail.com) by monty-python.gnu.org with esmtp (Exim 4.52) id 1FZa4L-00089T-Oq for help-gnu-emacs@gnu.org; Fri, 28 Apr 2006 17:00:05 -0400 Original-Received: by nproxy.gmail.com with SMTP id m19so1711298nfc for ; Fri, 28 Apr 2006 13:56:45 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=HofXGSahk8DX6Wt6AsHgGbR5Rco9+HDEz7podsEKoLbNK/Mo0ohFQQKajphsGphcXwWW7qY/U0fmRLfZnH2ubOGg7EmeGCVf0VED6ojMYzAyG26JxoYaSU+G+YIHrf/XfzizI4Sxo0b69pabf34gI7KpKRxQZFsM4ulnFqzn3/s= Original-Received: by 10.49.78.14 with SMTP id f14mr3108012nfl; Fri, 28 Apr 2006 13:56:45 -0700 (PDT) Original-Received: by 10.49.51.17 with HTTP; Fri, 28 Apr 2006 13:56:45 -0700 (PDT) Original-To: help-gnu-emacs@gnu.org In-Reply-To: <2cd46e7f0604281353l38f7672gd3cfe0c64fdf0cb4@mail.gmail.com> Content-Disposition: inline X-Mailman-Approved-At: Sat, 29 Apr 2006 02:02:32 -0400 X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:34711 Archived-At: i recently started noticing that emacs 22 regular expression isearches do not treat spaces exactly - any number of spaces in your search will map to any number, same or different, of spaces in the target. for example: - copy this message into an empty buffer - postiong the cursor at the beginning of the buffer - start an isearch (Ctrl-s) - toggle it to a regexp-isearch (Meta-r) - enter three spaces - enter an "s" when i do this, the cursor winds up positioned on the "s" at the beginning of the third word in this message, "started". i'm starting to realize that this behavior has been in emacs 22 for at least a while, and is not in emacs 21. can anyone tell me whether or not it's deliberate, and what the rationale is? (i started writing this up as a bug for emacs-devel, but looking into isearch-search and seeing that `search-spaces-regexp' is specifically set to the value of `search-whitespace-regexp' is making me suspect that the behavior is a deliberate design feature. ?) -- ken manheimer ken.manheimer@gmail.com http://myriadicity.net