From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Vincent Lefevre Newsgroups: gmane.emacs.bugs Subject: bug#58992: 28.2; "lax space matching" no longer works Date: Fri, 4 Nov 2022 03:29:50 +0100 Message-ID: <20221104022950.GJ9807@zira.vinc17.org> References: <87tu3gasjn.fsf@zira.vinc17.org> <83iljw6kbk.fsf@gnu.org> <20221103172157.GB9807@zira.vinc17.org> <83h6zf7w53.fsf@gnu.org> <20221103183316.GH9807@zira.vinc17.org> <837d0b7uce.fsf@gnu.org> <20221103185207.GI9807@zira.vinc17.org> <835yfv7sij.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="26341"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Mutt/2.2.7+51 (a318ca5a) vl-149028 (2022-10-21) Cc: 58992@debbugs.gnu.org To: Eli Zaretskii Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Fri Nov 04 03:30:22 2022 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 1oqmTN-0006gV-Iu for geb-bug-gnu-emacs@m.gmane-mx.org; Fri, 04 Nov 2022 03:30:21 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1oqmTA-0000Wn-Im; Thu, 03 Nov 2022 22:30:08 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1oqmT5-0000VZ-8Q for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 22:30:03 -0400 Original-Received: from debbugs.gnu.org ([209.51.188.43]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1oqmT4-0005Qc-Vj for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 22:30:02 -0400 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1oqmT4-0001Aj-O8 for bug-gnu-emacs@gnu.org; Thu, 03 Nov 2022 22:30:02 -0400 X-Loop: help-debbugs@gnu.org Resent-From: Vincent Lefevre Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 04 Nov 2022 02:30:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 58992 X-GNU-PR-Package: emacs Original-Received: via spool by 58992-submit@debbugs.gnu.org id=B58992.16675289954472 (code B ref 58992); Fri, 04 Nov 2022 02:30:02 +0000 Original-Received: (at 58992) by debbugs.gnu.org; 4 Nov 2022 02:29:55 +0000 Original-Received: from localhost ([127.0.0.1]:51167 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqmSw-0001A3-T4 for submit@debbugs.gnu.org; Thu, 03 Nov 2022 22:29:55 -0400 Original-Received: from joooj.vinc17.net ([155.133.131.76]:44514) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1oqmSu-00019t-LO for 58992@debbugs.gnu.org; Thu, 03 Nov 2022 22:29:53 -0400 Original-Received: from smtp-zira.vinc17.net (128.119.75.86.rev.sfr.net [86.75.119.128]) by joooj.vinc17.net (Postfix) with ESMTPSA id 845D7BD; Fri, 4 Nov 2022 03:29:50 +0100 (CET) Original-Received: by zira.vinc17.org (Postfix, from userid 1000) id 6432D2800196; Fri, 4 Nov 2022 03:29:50 +0100 (CET) Content-Disposition: inline In-Reply-To: <835yfv7sij.fsf@gnu.org> X-Mailer-Info: https://www.vinc17.net/mutt/ 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: , Original-Sender: "bug-gnu-emacs" Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.bugs:247035 Archived-At: On 2022-11-03 21:22:12 +0200, Eli Zaretskii wrote: > > Date: Thu, 3 Nov 2022 19:52:07 +0100 > > From: Vincent Lefevre > > Cc: 58992@debbugs.gnu.org > > > > > Yes. But in programming modes the newline didn't match. > > > > Any reason why (perhaps except for shell modes)? > > Because the newline's syntax is not "whitespace" in those modes. OK, but then, the question is why the newline's syntax is not "whitespace" in those modes... > > In C, except for the preprocessor, a newline is similar to a space > > character. > > The syntax we give to each character in a major mode depends on what > the mode needs to do with that character. For example, a mode might > have a good reason to give the newline the '>' syntax, because the > newline ends a comment in those modes. In C, the conventional comment is /* ... */ and the newline does not end a comment. In any case, /* ... */ is more practical to write multi-line comments in C (no need to repeat comment starters at the beginning of every line), and if one wants to search in comments, the newline should be regarded as a whitespace. > > BTW, it actually doesn't match either for the Texinfo mode, and > > I don't see any reason why. > > In which version of Emacs, and with what value of > search-whitespace-regexp? Both 27.1 and 28.2 (Debian for both), with search-whitespace-regexp set to "\\s-+". For Texinfo, it is more common to search in the normal text (rather than comments), since this is the significant content, so the newline character should be regarded as whitespace. -- Vincent Lefèvre - Web: 100% accessible validated (X)HTML - Blog: Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)