From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Artur Malabarba Newsgroups: gmane.emacs.devel Subject: Re: Please add comments to isearch.el Date: Fri, 11 Dec 2015 23:24:37 +0000 Message-ID: References: <83fuzoojcn.fsf@gnu.org> <83poyd8kta.fsf@gnu.org> <20151211121617.GA3351@acm.fritz.box> <83y4d16txk.fsf@gnu.org> <83lh916jpp.fsf@gnu.org> <871tasbnhh.fsf@mail.linkov.net> Reply-To: bruce.connor.am@gmail.com NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=001a11c2345e7a8d1a0526a7a095 X-Trace: ger.gmane.org 1449876298 26522 80.91.229.3 (11 Dec 2015 23:24:58 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 11 Dec 2015 23:24:58 +0000 (UTC) Cc: Alan Mackenzie , Eli Zaretskii , emacs-devel To: Juri Linkov Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Sat Dec 12 00:24:58 2015 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 1a7X3Y-00053X-Sv for ged-emacs-devel@m.gmane.org; Sat, 12 Dec 2015 00:24:57 +0100 Original-Received: from localhost ([::1]:49867 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7X3X-0005HT-Re for ged-emacs-devel@m.gmane.org; Fri, 11 Dec 2015 18:24:55 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:36515) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7X3I-0005HE-BF for emacs-devel@gnu.org; Fri, 11 Dec 2015 18:24:41 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a7X3H-00008A-KL for emacs-devel@gnu.org; Fri, 11 Dec 2015 18:24:40 -0500 Original-Received: from mail-lb0-x231.google.com ([2a00:1450:4010:c04::231]:35538) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a7X3G-00007l-41; Fri, 11 Dec 2015 18:24:38 -0500 Original-Received: by lbpu9 with SMTP id u9so72262786lbp.2; Fri, 11 Dec 2015 15:24:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:reply-to:sender:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=QXsmszDWwKnDfaSkPtxoaqQV55X/oYefT/hGlC0Gils=; b=QexjNdS491egg3k8eDbdzRXu4bOcqsSV93RHsjZCs9/5Vtp1R5qm3dQosKHSJ2H4L0 S4B4G2QuT+VqSfzGT7tG3axS5UZreF6Lk2kT3Sp+jyMi9Wb19Ez8BzrJDl4TAjM3ijWB 0s15rZHu0jB4MynzewWt5Zff6y0NnApRoOvh6Km4UhJ/ZqNCTjdt5Zom3Qu8gykbuPWw 3/ZQj9zFrJ36yEeNSXGZhw7obog9QWHStNJW61HCbZ9a2gYXlcPCmSEEMynrziFBXPQl nlJmGy1bRQ0Tiu9hdKYbAYxnIrcWXwTT/nE2RI4zNNoyCijKoPlMw2d/9MytclbxZTPm bfnw== X-Received: by 10.112.168.133 with SMTP id zw5mr8903397lbb.95.1449876277331; Fri, 11 Dec 2015 15:24:37 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Fri, 11 Dec 2015 15:24:37 -0800 (PST) Original-Received: by 10.112.202.99 with HTTP; Fri, 11 Dec 2015 15:24:37 -0800 (PST) In-Reply-To: <871tasbnhh.fsf@mail.linkov.net> X-Google-Sender-Auth: -AR_Pt1eGdFhXSsS0kRPyW8-hxo X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2a00:1450:4010:c04::231 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:196144 Archived-At: --001a11c2345e7a8d1a0526a7a095 Content-Type: text/plain; charset=UTF-8 On 11 Dec 2015 10:59 pm, "Juri Linkov" wrote: > > For example, the recent removal of a layer of indirection for lax-whitespace > broke customizations that allowed overriding search-forward-lax-whitespace > with own implementation to ignore all possible whitespace instead of > just spaces in the search string. How recent? Was that reported? --001a11c2345e7a8d1a0526a7a095 Content-Type: text/html; charset=UTF-8


On 11 Dec 2015 10:59 pm, "Juri Linkov" <juri@linkov.net> wrote:
>
> For example, the recent removal of a layer of indirection for lax-whitespace
> broke customizations that allowed overriding search-forward-lax-whitespace
> with own implementation to ignore all possible whitespace instead of
> just spaces in the search string.

How recent? Was that reported?

--001a11c2345e7a8d1a0526a7a095--