GNU bug report logs - #21278
char-fold isearch: space and newline

Previous Next

Full log

Message #73 received at 21278 <at> debbugs.gnu.org (full text, mbox):

From: Lars Ingebrigtsen <larsi <at> gnus.org>
To: Augusto Stoffel <arstoffel <at> gmail.com>
Cc: 21278 <at> debbugs.gnu.org, rms <at> gnu.org, bruce.connor.am <at> gmail.com,
 juri <at> linkov.net, monnier <at> iro.umontreal.ca, Eli Zaretskii <eliz <at> gnu.org>
Subject: Re: bug#21278: char-fold isearch: space and newline still broken
Date: Mon, 13 Sep 2021 09:26:01 +0200

Augusto Stoffel <arstoffel <at> gmail.com> writes:

>>> - not too lax: "[ \\t]+"
>>> - match across lines: "[ \\t\\n]+"
>>> - eat punctuation: "\\W+"
>>> - fuzzy: ".*?"
>>
>> I'm thing that trying to assign names to "[ \t]+" as "not too lax" will
>> just be more confusing than saying "tabs and spaces", and the same goes
>> for the other alternatives, too.
>
> Right, more serious names could be:
>
> 1. Tabs and spaces
> 2. Tabs, spaces and line breaks

OK, added.

> 3. Whitespace and punctuation

That has the same problem as this bug report -- it uses a syntax class.
(And it doesn't seem to have much to do with whitespace, which is what
this variable is about.

> 4. Any sequence of characters (fuzzy)

That doesn't seem to have anything to do with whitespace.

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.