From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: John Wiegley Newsgroups: gmane.emacs.bugs Subject: bug#22494: still can't search for two spaces Date: Wed, 03 Feb 2016 10:56:16 -0800 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> <450ada88-ae30-4cde-8db0-cc8e625eebf9@default> Reply-To: John Wiegley NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1454525843 30043 80.91.229.3 (3 Feb 2016 18:57:23 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 3 Feb 2016 18:57:23 +0000 (UTC) Cc: 22494@debbugs.gnu.org, mbork@mbork.pl, rms@gnu.org, jidanni@jidanni.org To: Drew Adams Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Wed Feb 03 19:57:10 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 1aR2c1-0005jf-6M for geb-bug-gnu-emacs@m.gmane.org; Wed, 03 Feb 2016 19:57:09 +0100 Original-Received: from localhost ([::1]:37065 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR2c0-00034d-DL for geb-bug-gnu-emacs@m.gmane.org; Wed, 03 Feb 2016 13:57:08 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:37536) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR2bx-00034V-8V for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2016 13:57:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1aR2bu-0000ZE-2O for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2016 13:57:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:49799) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1aR2bt-0000ZA-VH for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2016 13:57:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84) (envelope-from ) id 1aR2bt-0002QC-L0 for bug-gnu-emacs@gnu.org; Wed, 03 Feb 2016 13:57:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: John Wiegley Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Wed, 03 Feb 2016 18:57:01 +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.14545257879263 (code B ref 22494); Wed, 03 Feb 2016 18:57:01 +0000 Original-Received: (at 22494) by debbugs.gnu.org; 3 Feb 2016 18:56:27 +0000 Original-Received: from localhost ([127.0.0.1]:58388 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aR2bL-0002PK-2N for submit@debbugs.gnu.org; Wed, 03 Feb 2016 13:56:27 -0500 Original-Received: from mail-pf0-f173.google.com ([209.85.192.173]:36833) by debbugs.gnu.org with esmtp (Exim 4.84) (envelope-from ) id 1aR2bJ-0002P8-PJ for 22494@debbugs.gnu.org; Wed, 03 Feb 2016 13:56:26 -0500 Original-Received: by mail-pf0-f173.google.com with SMTP id n128so18135141pfn.3 for <22494@debbugs.gnu.org>; Wed, 03 Feb 2016 10:56:25 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:cc:subject:in-reply-to:date:message-id:references :user-agent:reply-to:mime-version:content-type; bh=y/h1pa9js5pyrneGFFU3hiKvw55MryVyMeiu2UWPzlE=; b=kVbzjXPFMpEiOXQZgmsUV1XZU30W3sbzLi8UJC/Bb20QutYh/XUark/v9L8PpptPdt lw8oZob0IrUYlfJ1iUIIlVD0QQu4cBaIP2eW2rsOa0Kh19K0fhETiJw3KdjZLLuTspkb G9LYefzEUsCImlMuJlrKfUL4NG+U0m5FO+7eJkoKew0zjfhCiLVqTwL1fMlmMjB+K0Vw v20SFTfppLcJmOLpqTKjjA5+RZW3h4Wi7q+OFJIQXJu46k1IbhPJL3hPIIKJSyMqkJwr 1paby0y+oSr4Y56iPwW8duFPbn8ymbvTh772Nkr3dzmQ5uYhX3YDtG2ofJ9uRgUPFMsb qjKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:in-reply-to:date:message-id :references:user-agent:reply-to:mime-version:content-type; bh=y/h1pa9js5pyrneGFFU3hiKvw55MryVyMeiu2UWPzlE=; b=F4ruNBOcqhO9Z7R0SO/lRzfifZcDQjDZl6xW6Fmi5qYmNksHm+zqNfMYAjmen5Vfl4 yJn7esUq6D5babxYDLVmiytpkQ24iVzaMMpyq2agX/CGAadSI9YwTkRAX89TC8yl0VA5 erLZd41I5K39st9Y7bnYUa071HB5wAvyHwWk3SNt3D3TxNxMZii+3tpSkxpuRaetRmzf EsCb1Y3syjR2WnR2pMcE6rIiwwv9HEXCWVRvwW4RUAyVt7BEvYyKKqYjKSI5+8xsZf1N joPGP+FqM6lqz6J/YQ7M6pW6nYs/B3Kn+qEH5rz5jd8GGbCLLekzrURKieAXfoas12Id umbA== X-Gm-Message-State: AG10YOSOTNI0ASXzo+sDso2BiNEiYKop+h0mxrRTl+yHeLjRGEwR5bjGEG1QX9W+69/jHA== X-Received: by 10.98.12.21 with SMTP id u21mr4673634pfi.36.1454525779940; Wed, 03 Feb 2016 10:56:19 -0800 (PST) Original-Received: from Vulcan.local (76-234-68-79.lightspeed.frokca.sbcglobal.net. [76.234.68.79]) by smtp.gmail.com with ESMTPSA id z67sm11495865pfa.71.2016.02.03.10.56.18 (version=TLS1 cipher=AES128-SHA bits=128/128); Wed, 03 Feb 2016 10:56:18 -0800 (PST) X-Google-Original-From: John Wiegley Original-Received: by Vulcan.local (Postfix, from userid 501) id 7C82A12BA3F19; Wed, 3 Feb 2016 10:56:17 -0800 (PST) In-Reply-To: <450ada88-ae30-4cde-8db0-cc8e625eebf9@default> (Drew Adams's message of "Wed, 3 Feb 2016 06:57:44 -0800 (PST)") User-Agent: Gnus/5.130014 (Ma Gnus v0.14) Emacs/24.5 (darwin) 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:112353 Archived-At: >>>>> Drew Adams writes: > Really? Always? I wouldn't have a problem with that (except if you mean for > it to apply also to regexp search). But those who are fans of lax whitespace > search might not like it. > Today, not only is lax whitespace matching a possibility, but it is the > default for C-s. What you suggest would mean that even with lax w-s > matching, search should first look for an exact match, before finding a lax > match (i.e., even if that lax match came before the literal match). Sorry, I wasn't entirely clear: I meant, if the user enters a search string which contravenes the notion of lax matching, such as two spaces. In the same way that we do for case folding. > 1. I agree (!) with the proposal to automatically turn OFF > lax w-s search if you type multiple, contiguous w-s chars. Yay! > 2. I proposed that when that happens we clearly indicate the > change to users. I'm fine with that too. > 3. I raised a question about whether lax w-s matching should > be automatically turned back ON if you change the search > string (e.g. delete some chars) so that it no longer has > multiple, contiguous w-s chars. I wonder about this too. > 4. I raised a question about whether lax w-s matching should > be automatically turned OFF if you _paste_ (not type) text > that contains multiple, contiguous w-s chars. I think it should be, as with typing them. > DWIM is hard. It never does what everyone means, in every context. It's > about compromises & judgment. And it requires good feedback about what it's > doing for "free". DWIM behind a user's back always bites someone, in the > end. ;-) > > Hope this clears things up a bit. Yes, very much, thanks Drew! -- John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2