From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Dani Moncayo Newsgroups: gmane.emacs.bugs Subject: bug#22494: still can't search for two spaces Date: Mon, 1 Feb 2016 15:15:55 +0100 Message-ID: References: <87h9hvshi3.fsf@jidanni.org> <54a07b7d-1fbd-4ed1-a8a0-e22eb5787c97@default> <871t8yit11.fsf@mbork.pl> <77b5b6df-4889-4142-a04d-526dd94c3a48@default> <6281db1e-d974-4cdc-b111-3e9097ae89db@default> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 X-Trace: ger.gmane.org 1454336243 29101 80.91.229.3 (1 Feb 2016 14:17:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 1 Feb 2016 14:17:23 +0000 (UTC) Cc: 22494@debbugs.gnu.org, mbork@mbork.pl, Richard Stallman , Dan Jacobson To: Andreas Schwab Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Mon Feb 01 15:17:14 2016 Return-path: Envelope-to: geb-bug-gnu-emacs@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 1aQFI0-00033l-1I for geb-bug-gnu-emacs@m.gmane.org; Mon, 01 Feb 2016 15:17:12 +0100 Original-Received: from localhost ([::1]:52658 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQFHy-0004em-Oz for geb-bug-gnu-emacs@m.gmane.org; Mon, 01 Feb 2016 09:17:10 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57606) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQFHu-0004ec-0X for bug-gnu-emacs@gnu.org; Mon, 01 Feb 2016 09:17:07 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aQFHq-0008Q6-Q8 for bug-gnu-emacs@gnu.org; Mon, 01 Feb 2016 09:17:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:55909) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aQFHq-0008Pz-Mc for bug-gnu-emacs@gnu.org; Mon, 01 Feb 2016 09:17:02 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aQFHq-0000TR-Ds for bug-gnu-emacs@gnu.org; Mon, 01 Feb 2016 09:17:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Dani Moncayo Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 01 Feb 2016 14:17:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 22494 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: notabug Original-Received: via spool by 22494-submit@debbugs.gnu.org id=B22494.14543361621735 (code B ref 22494); Mon, 01 Feb 2016 14:17:02 +0000 Original-Received: (at 22494) by debbugs.gnu.org; 1 Feb 2016 14:16:02 +0000 Original-Received: from localhost ([127.0.0.1]:44129 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aQFGs-0000Rs-38 for submit@debbugs.gnu.org; Mon, 01 Feb 2016 09:16:02 -0500 Original-Received: from mail-wm0-f52.google.com ([74.125.82.52]:34358) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aQFGq-0000RZ-Mz for 22494@debbugs.gnu.org; Mon, 01 Feb 2016 09:16:00 -0500 Original-Received: by mail-wm0-f52.google.com with SMTP id 128so73113284wmz.1 for <22494@debbugs.gnu.org>; Mon, 01 Feb 2016 06:16:00 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=jdHAlgFt/WhEqunu5L0DWL78rf3pfHJCXYDMLjctT3U=; b=l4/7MAFsqtWjFrnzGjkhXCKTWSGOBsP0gPCD99FBIA7a7/P4tbGioxKqfgjtpQnW8r Ka5eTAwSqqS5Fc1z+A6aAD0rNEXipXWBcI0X0nptM57mSsDyeMNaqDKE/AZdXKdlmSUg xSxQHeglNiMUODsQz1Q+ArpLGDZj/P3czXQPLDedJxt9D6yKSxflNDXBqbLwCP6Bzj0E 5xgk3WN/ZttcSnVLGYEchD+ONhWd3UtED7j7yAJSt3FxZ4t3TE7Cj7mAzJ1JG9MB9Hb8 vkeg4drnGtIJyU/49IgrsPJtAnFoRYDpOXHfDqWwjUZhKX6dpdtYbko9wPFB3+0K/LhO aDOQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=jdHAlgFt/WhEqunu5L0DWL78rf3pfHJCXYDMLjctT3U=; b=lm+tdwzmUWCYUbAQq3xZ356zjIx6lGVv0fVWdChb8Yk4G1wPQBs2lfLQRbC3SvEtQf OJWx+rnfbeOETxZN9sOYncveg4qiP3LKMLLpG2s8xDexlJJdMVcb/lLFFWjD5xp0q9rk U800EENii/N4G4jzCbmzS9hNAmQk0eoR7MUIeg9TmWDMmAOWpYsXP0ydpH40584Odgqf a8PCBWzzsdvWNjTLsIrcwPOt/qX/pe77efBHDWKjq4iCaanvrj3xEWHq9s4Lzr5wY7j7 +slf2OJa147Pe3gi3Lc0D8VpuF0+MMVC6pviYVErGecYIGNWgzG2/VKAstYedB+v7YdF FN4A== X-Gm-Message-State: AG10YOSiM5KcAO9Cdcrh+NI9eEmRXHS92f5spxBjPS6CEiIPZfidB/CvFPKVRxnAnMhpzlTdNfxqzJzrp8ElKA== X-Received: by 10.194.242.67 with SMTP id wo3mr22204303wjc.180.1454336155076; Mon, 01 Feb 2016 06:15:55 -0800 (PST) Original-Received: by 10.27.225.4 with HTTP; Mon, 1 Feb 2016 06:15:55 -0800 (PST) In-Reply-To: X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:112201 Archived-At: >> > What is in the search string is a search pattern. How it is >> > interpreted is the question. >> >> Right. And I am proposing a way to interpret part of it. Namely, >> two spaces in a row means to match two spaces in the buffer. > > But if you isearch-yank them they should be normalized so that they > continue to do lax matching. Quoting from [1]: IMO, Emacs should refrain from making permanent changes to the search string, as given by the user. IOW, the search string should be kept untouched, and any transformations of it should be done "on the fly" to achieve the intended behavior, based on both the _current_ search string and the _current_ user options that govern the search behavior. That way, if/when either the search string or the user options changes, Emacs will be able to exhibit the expected behavior. IOW, I don't think that normalization is a good idea. But I agree with you that two (or more) consecutive spaces should be treated specially _only_ if they were *typed* by the user (not yanked from the kill ring or grabbed from the buffer) --- Dani Moncayo [1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=16546#43