unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: 40216@debbugs.gnu.org
Subject: bug#40216: 28.0.50; Misinformation in isearch char-fold
Date: Thu, 26 Mar 2020 10:28:55 +0100	[thread overview]
Message-ID: <m2imirea7c.fsf@gmail.com> (raw)
In-Reply-To: <87imiskzc6.fsf@mail.linkov.net> (Juri Linkov's message of "Wed,  25 Mar 2020 22:29:29 +0200")

>>>>> On Wed, 25 Mar 2020 22:29:29 +0200, Juri Linkov <juri@linkov.net> said:

    >> Out of curiosity, what were you searching for that resulted in such a
    >> large regexp?

    Juri> Sometimes I pull a few of lines (usually 1-3 lines, not more)
    Juri> from the buffer into the search string to confirm that the same lines
    Juri> exist in more places in the same buffer ignoring the differences defined
    Juri> by folding rules.  But after pulling 2 lines into the search string,
    Juri> the generated regexp becomes so long that the regexp search fails
    Juri> with the error "Regular expression too big".  Currently it silently
    Juri> switches to literal search without notification that it doesn't follow
    Juri> the folding rules anymore.  With the patch it informs about switching
    Juri> to literal search.

Ah, I hadn't considered that use case. Do we need an option to
char-fold-regexp that says 'only apply char-folding to non-ascii
characters'? That would reduce the size of the regexp considerably.

Robert





  reply	other threads:[~2020-03-26  9:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-24 23:00 bug#40216: 28.0.50; Misinformation in isearch char-fold Juri Linkov
2020-03-25  9:22 ` Robert Pluim
2020-03-25 20:29   ` Juri Linkov
2020-03-26  9:28     ` Robert Pluim [this message]
2020-03-26 14:25       ` Eli Zaretskii
2020-03-26 15:43         ` Robert Pluim
2020-03-26 23:04           ` Juri Linkov
2020-03-27  7:24             ` Eli Zaretskii
2020-03-27  8:30               ` Robert Pluim
2020-03-28 23:42                 ` Juri Linkov
2020-03-26 23:00       ` Juri Linkov

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=m2imirea7c.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=40216@debbugs.gnu.org \
    --cc=juri@linkov.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).