From: Juri Linkov <juri@linkov.net>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: 63272@debbugs.gnu.org
Subject: bug#63272: 29.0.90; xref fails on long lines
Date: Fri, 05 May 2023 20:50:19 +0300 [thread overview]
Message-ID: <86354a1xd0.fsf@mail.linkov.net> (raw)
In-Reply-To: <7393ccd9-f32f-9ce9-7159-e0fe6e1e1fef@gutov.dev> (Dmitry Gutov's message of "Thu, 4 May 2023 18:33:17 +0300")
tags 63272 notabug
close 63272 29.0.60
thanks
>> 1. Create a file with a long line, e.g. type
>> a C-u 500000 b c
>> Save the file and commit to git.
>> (long-line-optimizations-p returns t)
>> 2. Try to search a regexp that matches the whole long line, e.g.
>> C-x p g a.*c RET
>> Debugger entered--Lisp error: (error "Stack overflow in regexp matcher")
>
> Isn't that more like a problem with the regexp you entered, or with our
> regexp engine?
>
> E.g. try this:
>
> C-x p g a[^c]*c RET
In the real case the prefix and suffix were unique, so I didn't expect
that in a generated file there was a very long distance between prefix
and suffix. To limit the distance between prefix and suffix I tried:
C-x p g prefix.{0,100}suffix
but xref that uses ripgrep fails to find matches.
So needed to fall back to ripgrep-based rgrep in this case:
M-x rgrep prefix.{0,100}suffix
that works successfully.
It seems the problem is because of different regexp syntax
used by ripgrep and re-search-forward in xref--collect-matches-1.
Since this is a separate problem, I'm closing this one,
then a new feature request could be opened if you want.
next prev parent reply other threads:[~2023-05-05 17:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 15:07 bug#63272: 29.0.90; xref fails on long lines Juri Linkov
2023-05-04 15:33 ` Dmitry Gutov
2023-05-05 17:50 ` Juri Linkov [this message]
2023-05-05 20:49 ` Dmitry Gutov
2023-05-08 15:41 ` Juri Linkov
2023-05-08 18:59 ` Dmitry Gutov
2023-05-04 15:58 ` Gregory Heytings
2023-05-05 9:13 ` Gregory Heytings
2023-05-05 17:39 ` 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=86354a1xd0.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=63272@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
/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).