From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: =?UTF-8?Q?K=C3=A9vin?= Le Gouguec Newsgroups: gmane.emacs.bugs Subject: bug#21278: char-fold isearch: space and newline still broken Date: Fri, 10 Sep 2021 15:17:19 +0200 Message-ID: <87h7esefj4.fsf@gmail.com> References: <8735qku8ic.fsf@gnus.org> <83o896s0qf.fsf@gnu.org> <83sfygq54m.fsf@gnu.org> <87ee9xu2tm.fsf@mail.linkov.net> <87pmtgragr.fsf@gnus.org> <83tuisitux.fsf@gnu.org> <87y284puka.fsf@gnus.org> <87v938ej9i.fsf@gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="23990"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: 21278@debbugs.gnu.org, rms@gnu.org, bruce.connor.am@gmail.com, juri@linkov.net, monnier@iro.umontreal.ca, Lars Ingebrigtsen To: Augusto Stoffel Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Sep 10 15:25:19 2021 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mOgWt-0005xt-BR for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 10 Sep 2021 15:25:19 +0200 Original-Received: from localhost ([::1]:45818 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1mOgWs-0004HN-2W for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 10 Sep 2021 09:25:18 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:47388) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1mOgPp-0008Nj-Uf for bug-gnu-emacs@gnu.org; Fri, 10 Sep 2021 09:18:02 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]:53943) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1mOgPp-00056v-LB for bug-gnu-emacs@gnu.org; Fri, 10 Sep 2021 09:18:01 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1mOgPp-0006fJ-HJ for bug-gnu-emacs@gnu.org; Fri, 10 Sep 2021 09:18:01 -0400 X-Loop: help-debbugs@gnu.org Resent-From: =?UTF-8?Q?K=C3=A9vin?= Le Gouguec Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 10 Sep 2021 13:18:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 21278 X-GNU-PR-Package: emacs Original-Received: via spool by 21278-submit@debbugs.gnu.org id=B21278.163127984825575 (code B ref 21278); Fri, 10 Sep 2021 13:18:01 +0000 Original-Received: (at 21278) by debbugs.gnu.org; 10 Sep 2021 13:17:28 +0000 Original-Received: from localhost ([127.0.0.1]:37256 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mOgPI-0006eR-K8 for submit@debbugs.gnu.org; Fri, 10 Sep 2021 09:17:28 -0400 Original-Received: from mail-wr1-f44.google.com ([209.85.221.44]:36582) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1mOgPG-0006eC-4O for 21278@debbugs.gnu.org; Fri, 10 Sep 2021 09:17:27 -0400 Original-Received: by mail-wr1-f44.google.com with SMTP id g16so2609024wrb.3 for <21278@debbugs.gnu.org>; Fri, 10 Sep 2021 06:17:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=from:to:cc:subject:references:date:in-reply-to:message-id :user-agent:mime-version:content-transfer-encoding; bh=5w0o249abL3j5LcyIwjqRN2jBuW5npb8lL7d0PTzygs=; b=W5jAVI41L0+ihKhxpiKh41c107mFVToUpPwVZpp0kh1HC9W8xMZSbYQQpozU3OwEgA I5Kui68pYApFQR4UN2WatpVmyKA3WnT7xAAulb3sZQCb9+B+HaYEWxgOFq9qMcAvX1Gs 2bjtg72wCNnnrYosQVkTaLNNa4cFl5vx3eNGobdLlW9LUhId0RzJYeKbUTuaS4E9axej 0lkU6EGTtgwMpYerAA7o0lMq4Arep401FZoMlXlA6rH0ArfEzDiEnsKvcx/mUb3SmB4F +wwBDvE1XserLs2taZHquJ7D9awGzJWAcd17oX8nRXDf4l60DFJ4IMkzWxbGjObXHH3+ AKxA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:references:date:in-reply-to :message-id:user-agent:mime-version:content-transfer-encoding; bh=5w0o249abL3j5LcyIwjqRN2jBuW5npb8lL7d0PTzygs=; b=rzS6F303PHRny6Rp4G/2vWrvS2oY0liwfFboapNuIIS2HcLRBHZr7aDhgpqMNeM1OK DpxkEF/+5S/WSH/taXN1olumHTrLoMoqOKAKmsNyHv3vPv68CzPDdAdUlPNPF2trA6F3 LLxeLqxP8TcmnDLQli3Txq4qso87mAlaNdK97+EV9rIWP5tPdbp04Z9BmihphNt3iO1Y RxQG+zpguYNSrKzsw7ZjpP9LNLTAuI68INHh2a0+nmbNRJAwsX0BZY55CuEL/Qa5OVLZ B9T/zWRCCS2LlO3O5DmuB5CuYwNUPF17Er3NEJhiMl/n4R39ysNt/jnfGQN+40HVEkVZ uiFg== X-Gm-Message-State: AOAM530yWJ7Ip8wZR1dBAlVKYCgdItTWsCsKlRNP/zZamdfXgoHgh60u lUcjrDNxtsCtAOmBBKwKCO4= X-Google-Smtp-Source: ABdhPJxp2mf90FHfZTxooutHUqZOLu60InP5Ykscb+MOSt/jmpTXjj+hcuyqnNLT9mPUJB00uxHMcw== X-Received: by 2002:a5d:404b:: with SMTP id w11mr4378822wrp.437.1631279840488; Fri, 10 Sep 2021 06:17:20 -0700 (PDT) Original-Received: from amdahl30 ([2a01:e0a:20e:d340:2ef0:5dff:fed2:7b49]) by smtp.gmail.com with ESMTPSA id t23sm4895490wrb.71.2021.09.10.06.17.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 10 Sep 2021 06:17:20 -0700 (PDT) In-Reply-To: <87v938ej9i.fsf@gmail.com> (Augusto Stoffel's message of "Fri, 10 Sep 2021 13:56:41 +0200") X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list 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-mx.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.io gmane.emacs.bugs:214008 Archived-At: Augusto Stoffel writes: > On Fri, 10 Sep 2021 at 12:57, Lars Ingebrigtsen wrote: > >> Eli Zaretskii writes: >> >>>> It seems like everybody agrees that the old value was confusing, so I'= ve >>>> now changed it to [ \t] in Emacs 28. >>> >>> Shouldn't it be [ \t]+ instead? >> >> Oops. Looks like I'm going for the "most errors in a trivial one-line >> patch" record here... > > For the record, search-whitespace-regexp could have more useful values > suggested in customize. I can think of: > > - not too lax: "[ \\t]+" > - match across lines: "[ \\t\\n]+" > - eat punctuation: "\\W+" > - fuzzy: ".*?" Seconded. I expect this to be a common customization: when searching for compound expressions ("regular expression", "environment variable"=E2= =80=A6) through prose filled using hard newlines (manpages, info nodes, docstrings=E2=80=A6), I have always found it useful for isearch to treat newlines as regular whitespace. If isearch no longer behaves like that by default, I'm sure users would at least appreciate Customize suggesting some ready-made values.